Breaking out of delivery mode
Too many designers get stuck in delivery mode. Learn the three habits that help you transition from delivering designs to shaping direction and building strategic influence.
Too many designers get stuck in delivery mode. It limits their influence. And it limits their career.
The most valuable designers aren’t just delivering designs. They’re shaping direction.
The good news is, this isn’t out of reach. You don’t need a new title or permission to start. You need to build the habits that make you a strategic partner.
The three habits of strategic partners
To become a more strategic partner, focus on these three habits:
- Be heavily involved in product discovery
- Gather and report customer feedback
- Talk to stakeholders
Use all of that context to deliver insights, not just designs, and use your design skills to create a vision of the future.
Habit 1: Be heavily involved in product discovery
The common issue I hear is, “My PM already does this.” If you’re leaving this entirely to a PM, start splitting up responsibilities now, but do it from an attitude of support and humility: “I’m interested in doing more discovery work. Can I help you out by dividing up the work?” Not from entitlement: “I should be doing this; it’s a designer’s job as well.”
Understand their process. If they’re more senior and you haven’t done much discovery work, help and learn. Otherwise, see if you can augment it with your own additions.
How to approach your PM about discovery
Instead of saying: “I should be doing this; it’s a designer’s job as well.”
Try saying: “I’m interested in doing more discovery work. Can I help you out by dividing up the work?”
If you want this collaboration to last, highlight how their contributions have helped you achieve better results. Praise them publicly, share how the collaboration benefits the designs, and highlight their contributions.
When you’re involved in discovery, you’re not just executing on requirements: you’re helping shape what gets built. This is where your influence grows.
Habit 2: Gather and report customer feedback
Ideally, this means talking to customers directly. But there are also other ways to get insights:
- Support chats and ticket logs
- Sales call recordings or notes
- Product reviews and app store feedback
- Social media mentions and conversations
- Surveys and user research sessions
- User testing and usability studies
Reporting on these insights helps shape the future of the product, increasing the value and scope of your contributions and shifting you more towards a knowledge worker than a pure delivery worker.
Creating insight reports
When you gather customer feedback, don’t just collect it: synthesise it into insights. Create regular reports that:
- Identify patterns across multiple sources
- Highlight the most impactful findings
- Suggest what these insights mean for the product
- Recommend next steps or areas to explore
Share these reports with your team. Over time, people will start looking to you for customer insights, not just designs.
Habit 3: Talk to stakeholders
To use your design skills to create a vision of the product’s future, you need to talk to product and engineering leadership to understand their goals and what’s feasible. That way, you can ensure that whatever artefacts you create are practical, aligned with their ideas, and can be used in conversations that build alignment.
Stakeholder interviews aren’t just about gathering requirements: they’re about building relationships, understanding constraints, and creating buy-in before you present work.
Who to talk to
Key stakeholders to engage with include:
- Product managers: understand roadmaps, priorities, and business goals
- Engineering leads: learn technical constraints and feasibility
- Business leaders: understand revenue goals and strategic direction
- Sales and support teams: hear direct customer feedback and pain points
- Other designers: understand existing patterns and design system constraints
Using context to deliver insights, not just designs
Once you’ve built these habits, you’ll have more context than most people on your team. The key is to use that context to deliver insights, not just designs.
Instead of just presenting a solution, share what you learned:
- “Based on customer interviews, I learned that users struggle with X because of Y”
- “Support tickets show this is a major pain point, with 40% of tickets related to this”
- “Stakeholders are concerned about Z, so I’ve addressed that in this design”
- “Engineering mentioned this constraint, so I’ve designed around it”
This shifts you from being someone who executes to someone who understands and informs.
Creating a vision of the future
With all this context, you can use your design skills to create a vision of the future. Not just what the product should look like, but what it should do, how it should feel, and how it should serve both users and business goals.
When you have deep context about customer needs, business goals, and technical constraints, your designs become more strategic. They’re not just pretty interfaces: they’re solutions to real problems that serve real business objectives.
Example: Instead of just designing a new feature because it was requested, you might say: “Based on customer feedback, users need a way to do X. But after talking to engineering, I learned we can achieve this more efficiently by doing Y. And stakeholders are focused on Z metric, so I’ve designed this to support that goal. Here’s my proposal.”
The shift: from delivery to direction
When you build these three habits, you shift from being a delivery person to being a strategic partner.
Delivery mode
- Waiting for requirements
- Executing on briefs
- Presenting finished designs
- Fixing what’s broken
- Reacting to requests
Strategic partner mode
- Shaping requirements
- Questioning briefs and proposing alternatives
- Sharing insights and recommendations
- Preventing problems before they happen
- Proactively identifying opportunities
Getting started: pick one habit
You don’t need to master all three habits at once. Start with the one that feels most achievable in your current role:
- If your PM is open to collaboration: Start with discovery. Offer to help with user interviews or research synthesis.
- If you have access to customers: Start by gathering and reporting feedback. Create a monthly insights report.
- If you need to build relationships: Start with stakeholder interviews. Schedule 30-minute conversations to understand goals and constraints.
Once one habit is established, add the next. Over time, you’ll have the context and relationships to be truly strategic.
Remember: it’s about habits, not titles
You don’t need a new title or permission to start building these habits. You just need to start. The more you practice them, the more you’ll be seen as a strategic partner. And that recognition often leads to the title change you’re looking for.
The difference between a delivery person and a strategic partner isn’t the work you’re assigned: it’s the work you choose to do. Start choosing differently today.