AWS re:Invent 2025 - The Builder's Job Is Not to Build: A Mindset for Better Outcomes (DEV347)

Shifting the Builder's Mindset: Focusing on Outcomes Over Outputs

Understanding Mindset

• Mindset is about how you approach the world, both your explicit thinking and implicit approach
• Key questions to reveal mindset:
  • Who am I? (identity)
  • What do I do? (function)
  • How do I respond to changes?

The Value of Discussing Mindset

• Mindset is crucial for practices like continuous deployment
  • Requires accountability, humility, and introspection
• Humility and self-confidence are not mutually exclusive

Typical Builder Mindsets

• Identifying with tools (e.g. VI vs Emacs, SQL vs NoSQL)
• Identifying with output (e.g. "my baby", not invented here syndrome)
• Being isolated from greater purpose

Adopting a Better Mindset

• Shift from "what do I do?" to "what are the outcomes I create?"
• Features are the asset, implementations are the liability
• Understand your place in the value chain and how you serve the customer

Applying the Outcome-Focused Mindset

Technology Selection

• View tools as means to an end, not part of identity
• Focus on total cost of ownership, not just upfront costs
• Strategically use "tech debt" to achieve faster time to market

Productivity and Flow

• Feelings of productivity are a poor proxy for actual productivity
• Spending time on less enjoyable tasks can lead to better long-term outcomes

Organizational and Technology Transformation

• Don't be attached to your outputs - be willing to "joyously" throw away code
• Understand how you fit into the organization's changing needs and outcomes

The Impact of AI

• AI shifts responsibility but not accountability
• AI can enable junior engineers but also risks them not developing necessary skills
• AI changes the cost-quality tradeoff, allowing lower-quality software at lower cost

Key Takeaways

• Builders are problem solvers, not artisans - the focus should be on outcomes, not outputs
• Adopt a mindset of adaptability, humility, and accountability to achieve better results
• Leverage tools and technologies as means to an end, not as part of your identity
• Be willing to let go of past outputs and focus on serving the organization's evolving needs
• Understand how AI can both enable and constrain your approach to building software