Strategy is choice: Deciding where product design should focus

10 minutes

How I reconsidered my 2027 product design strategy when business priorities, team capabilities, and organisational constraints forced me to make more deliberate choices.

This is part 2 of my series on planning product design for the year ahead, inspired by Playing to Win. In part 1, I explored how design goals become business commitments. Here, I examine the choices required to make those commitments realistic.

When the team you planned for is not the team you have

When I started planning our product design organisation for 2027, my first instinct was to understand everything we needed to support. Our customers interact with us through websites, mobile applications, branches, contact centres, emails, and conversational interfaces. Employees also rely on internal platforms to support those customers.

I began exploring how we could strengthen ownership across acquisition, servicing, omnichannel experiences, and internal platforms, alongside the specialist capabilities needed to support them. Each area represented a genuine need. But I eventually recognised a problem.

I was designing an organisation around the work that existed, rather than the strategic choices we were prepared to make.

As planning progressed, I realised that my initial vision depended on resources beyond what we could realistically commit to. I needed to reconsider our priorities around the team we had and the outcomes we could meaningfully influence. Instead of asking what the ideal organisation should look like, I began asking:

Given our business objectives, customer evidence, and existing capabilities, where can product design make the greatest contribution?

That question changed my approach to planning.


A roadmap is not a strategy

Around the same time, I was reading Playing to Win: How Strategy Really Works by A.G. Lafley and Roger L. Martin. The book challenged how I had historically approached annual planning. I had created roadmaps, objectives, and presentations that explained what needed to happen. But I started questioning whether those documents adequately explained why.

  • Could my designers explain how their work contributed to business outcomes?
  • Did they understand why one customer problem deserved attention over another?
  • Could they advocate for those priorities without relying on me?

I realised that a roadmap could organise work without providing strategic direction. A roadmap explains what we intend to deliver and when. A strategy explains where we have chosen to focus, why those choices matter, what capabilities we need, and how we intend to create value. That distinction became central to how I approached our 2027 planning.


Not every business priority deserves equal design investment

Diagram showing business opportunities evaluated against business value, customer evidence, and team capability, resulting in three design commitments: lead, consult, or reprioritise.
Strategic priorities emerge where business value, customer evidence, and organisational capabilities intersect.

Every business objective can be important without requiring the same level of investment from product design. Our organisation had several priorities, from improving established products to exploring new opportunities. Each presented potential value, but we could not approach them all with equal commitment.

I evaluated opportunities against three considerations:

  1. Business value: Where could design contribute to measurable company objectives?
  2. Customer evidence: Where did we understand the problems, and what still needed investigation?
  3. Team capability: What could our existing team realistically research, design, validate, and support?

These considerations helped narrow our focus towards established customer experiences with meaningful evidence and opportunities to improve measurable outcomes. But making that choice also meant deciding what we would not prioritise.

A strategy becomes more credible when it explains what the team will not prioritise, as clearly as what it will.

I discussed these choices with leadership, challenged assumptions, and negotiated where we could concentrate our efforts. The objective was not simply to protect my team’s capacity. It was to protect the organisation’s investment in the work we had agreed mattered most. Changing priorities has consequences. Designers develop knowledge about customer behaviours, business rules, and technical dependencies. Repeatedly interrupting that work affects delivery speed and decision quality. I wanted those trade-offs to be understood before we accepted additional commitments.


The evidence was already there, but it was scattered

Diagram showing research from support, product, marketing, technology, and compliance feeding a shared evidence assessment, with findings classified as confirmed insights, directional insights, and evidence gaps.
Connecting existing research helps teams challenge assumptions and identify what still needs investigation.

One thing I have learned from working across larger organisations is that customer evidence rarely belongs to one department. Marketing may have customer research. Product teams have analytics. Technology understands recurring system limitations. Compliance has regulatory insights. Customer support teams hear directly about the problems people encounter. The challenge is that these findings often remain within their respective departments.

Before commissioning additional research, I started connecting with colleagues, requesting existing reports, and bringing relevant findings together. I separated evidence that could inform decisions from directional signals requiring validation and questions that remained unanswered. One example involved a discussion about becoming more relevant to a particular customer segment. The initial assumption focused on brand perception. But reviewing existing research raised questions about whether the underlying problem was actually related to the experience customers received. Customers wanted greater clarity about costs, requirements, and what to expect throughout a digital process.

That changed how I interpreted the opportunity. Rather than beginning with a proposed brand solution, we needed to investigate whether the product experience was meeting customer expectations. The evidence did not settle the decision. It helped us ask better questions before committing resources.

A new identity might change how customers perceive a product. But it cannot replace the need to understand whether the experience delivers the clarity, functionality, and trust customers expect.

This reinforced an important lesson: the problem initially presented to design is not always the problem we should solve. Bringing evidence together helps us challenge assumptions, identify gaps, and determine where further investigation will create value.


Establish a baseline before committing to solutions

Another change involved how I wanted my designers to approach their responsibilities. Understanding users and exploring solutions remain fundamental to design. But connecting those activities to measurable outcomes requires us to understand current performance.

Before recommending changes, I wanted the team to ask:

  • What is happening today, and who is affected?
  • What evidence explains the problem?
  • What would meaningful improvement look like?
  • How will we know if our intervention worked?

Sometimes the data exists but is difficult to interpret. Sometimes we have qualitative evidence without reliable measurements. Other times, we need further research before identifying the right opportunity. I did not want incomplete information to prevent progress. But I also did not want us making commitments based on untested assumptions. For priority experiences, I began identifying existing evidence, missing measurements, and research questions that designers could investigate.

This changed how I thought about ownership. A designer should not be responsible only for producing a solution. They should understand the problem, evaluate alternatives with partners, and contribute to learning from the outcome. Business results depend on multiple functions. I do not expect designers to claim sole responsibility for conversion or revenue. I do expect them to understand how their decisions contribute to those outcomes.

If we cannot explain the starting point, we should be careful about claiming progress.


Strategic focus does not mean abandoning other channels

One difficult part of narrowing our priorities was determining how product design would continue supporting experiences outside our primary focus. Our responsibility extended across several customer and employee-facing channels. Each had legitimate needs, but our available capacity required a more deliberate approach. Working with leadership, I distinguished between areas requiring direct design ownership and those better supported through consultation.

For priority experiences, designers would lead research, problem definition, experience design, validation, and implementation collaboration. For other areas, we could provide guidance, review proposed experiences, recommend established patterns, and help teams evaluate usability, accessibility, and customer impact. More complex requests would require a conversation about capacity and existing commitments.

Our direction was digital-first, not digital-only.

Customers do not think about their experiences according to organisational boundaries. Someone might begin an application online and later contact support or visit a branch for assistance. Understanding those interactions remains important, even when our investment is concentrated elsewhere. I began discussing the approach with channel owners and cross-functional partners. I wanted them to understand where design would lead, where we would advise, and how additional requests would be evaluated. I also wanted their input on dependencies or upcoming needs we might have overlooked. These conversations helped establish expectations before the roadmap became a collection of competing requests.

Strategic focus is not about saying no to collaboration. It is about being clear on where you lead, where you advise, and what needs to change when the organisation asks you to do more.


A strategy needs to make sense to the team delivering it

I could spend weeks evaluating evidence, discussing priorities, and negotiating commitments. But if my designers did not understand the reasoning, the strategy would remain dependent on me. That was not the outcome I wanted. I began separating our strategic choices from our roadmap. The strategy explained where we would focus, why those priorities mattered, what capabilities we needed, and how we would evaluate progress. The roadmap translated those choices into objectives, responsibilities, and delivery commitments. I also wanted designers to challenge the plan when evidence contradicted our assumptions.

One question from Playing to Win became particularly useful:

What would have to be true for this strategy to succeed?

For our direction to work, we needed sufficient customer evidence, meaningful performance measures, available team capabilities, cross-functional support, and leadership agreement on trade-offs. These were conditions to validate, not assumptions to leave hidden in a presentation. New evidence will emerge. Some interventions will work, and others will not. A strategy should provide a basis for evaluating those changes rather than prevent us from responding to them.


Five questions for design leaders

Looking back, I would encourage other design leaders to consider five questions before finalising their annual roadmaps.

  1. Are you planning around the capabilities you have?
    An ideal team structure should not become the foundation of commitments you cannot deliver.
  2. Have you distinguished business importance from design investment?
    Not every objective requires equal design ownership.
  3. What evidence supports your priorities?
    Review existing research and identify what still needs validation.
  4. Do your partners understand the trade-offs?
    Agree on how new requests will affect existing commitments.
  5. Can your designers explain the strategy without you?
    They should understand the reasoning, not only the deliverables.

I began planning with an ambitious view of the organisation I wanted to build. Those needs have not disappeared, but the constraints pushed me to become more deliberate about the decisions we could make today. Reading Playing to Win helped me recognise that this was not simply a compromise driven by organisational constraints. It was an opportunity to clarify where product design could create meaningful value.

Strategy is not the collection of everything we believe should happen. It is the set of choices we are prepared to support, explain, and act upon.

For me, that has become one of the most important responsibilities of design leadership. Next, I will explore how those choices influence the capabilities, responsibilities, and operating model a design team needs to deliver on its strategy.

Let’s keep learning together

I share my experiences and lessons in product design, leadership, and building teams that create meaningful impact. If these perspectives are useful, follow me on LinkedIn for more articles and conversations. If you’re working through a design challenge, looking for career guidance, or interested in developing your skills, explore my mentorship sessions. Or simply get in touch. I’m always happy to exchange ideas, share what I’ve learned, and help others approach challenges from a different perspective.