Thinking Like a PM: Getting the Best Out of UX Workflows
#projectmanagement #uxops #workflowdesign
by Sebastiano Piras
UX design is often seen as fluid, creative, and nonlinear — and it is. But when creative processes collide with delivery frameworks, things get stuck. Designers lose momentum. Developers build misaligned features. Stakeholders get lost in the noise.
These breakdowns don’t always stem from weak ideas or flawed execution. Often, they reflect an underlying gap in coordination — a lack of shared rhythm between exploration and delivery. While design thrives in ambiguity, product teams need anchors: scope, milestones, ownership, measurable outcomes.
That doesn’t mean forcing UX into rigid Gantt charts or turning ideation into admin. It means supporting creativity with structure. It means designing processes as thoughtfully as we design interfaces.
Bringing a project management mindset into UX workflows helps teams move from ideas to impact. Not by restricting design, but by making it more actionable, more visible, and more aligned with strategy.
Here is how simple shifts — from task lists to problem framing, from specs to stories — can make UX work more collaborative, grounded, and effective.
The approach draws on adaptive practices that help teams turn uncertainty into shared clarity. From strategic roadmaps to lightweight planning tools, the goal is to support creative thinking with just enough structure to move from vision to execution without losing momentum along the way.
Reframing UX as a Strategic Initiative
Too often, design starts with artifacts — a screen, a wireframe, a visual direction — rather than with alignment. But UX gains traction when it’s framed as a strategic initiative, not just a creative phase. Before any design takes shape, there should be a shared understanding of what matters, why it matters, and who it’s meant to serve.
This reframing begins by asking different questions:
- What problem are we solving?
- Who needs to be involved to solve it?
- How does this support our product or business goals?
Early alignment sessions or planning canvases can help surface these answers. Whether through a one-page brief, a kickoff canvas, or a stakeholder map, the goal is to align on purpose, priorities, and constraints before diving into execution. This helps prevent the “design silo” problem, where decisions are made without shared context or clarity.
When UX work follows a strategic arc, grounded in purpose and measurable intent, it becomes easier to scope, staff, and integrate. It stops being a parallel process and starts becoming core to delivery. That shift sets the foundation for everything else to flow better.
This reflects a core Agile principle: “Welcome changing requirements, even late in development.” With early alignment, teams are more resilient to change and less reactive under pressure.
Design Around Problems, Not Tasks
Design backlogs tend to sprawl. What begins as a few key ideas can quickly grow into endless lists of screens, states, components, and edge cases. In the middle of those lists, the why often gets buried beneath the what — and that’s where alignment starts to slip.
Project managers take a different approach. They structure work around problems to solve, not just features to ship. This framing helps shape how teams collaborate, what research gets surfaced, and which trade-offs make sense.
One practical way to apply this mindset in UX is through the Now / Next / Later roadmap.
Rather than forcing speculative features into artificial deadlines, this format groups work by priority and confidence:
Now: Problems actively being explored or solved
Next: Opportunities validated, but not yet staffed or scoped
Later: Signals worth watching, but too early to act on
This format, popularized by Janna Bastow (co-founder of ProdPad and Mind the Product), helps agile teams balance short-term focus with long-term vision. It treats the roadmap as a prototype for strategy — not a rigid schedule.
It helps teams remain strategic without overcommitting. It clarifies expectations for stakeholders and preserves space for exploration.
It may remind you of the MoSCoW method, since both organize tasks in visual columns. But while MoSCoW focuses on delivery categories like Must have or Should have, Now / Next / Later aligns priority with confidence and time sensitivity. It’s more flexible for early discovery phases and shifting product landscapes.
Problems give designers room to explore. Lists only tell them what to deliver.
Clarify Work with Stories, Not Specs
Designers are naturally visual thinkers — but in cross-functional teams, visuals alone aren’t enough. Figma files don’t always explain why something matters. Specs can list components, but they rarely express context or intent. That’s where user stories come in.
Stories offer a shared language between designers, developers, and product managers. They translate UX thinking into delivery-ready insights. Instead of handing off mockups or writing lengthy functional specs, teams can align on intent, outcomes, and user value.
A strong user story for UX doesn’t describe what’s on the screen — it describes what the user needs to achieve, and why:
As a [type of user], I want to [do something], so I can [achieve a goal].
For example: As a returning customer, I want to skip onboarding, so I can start using the app immediately.
But that’s just the starting point. The real power comes from extending stories with supporting detail. These stories should also include clear acceptance criteria — specific requirements that define when the experience is considered complete. Criteria might span user needs, technical conditions, or success metrics agreed with the product team.
Other useful additions to a UX-focused user story include:
Link the story to relevant research insights or usability findings
Add a definition of done from both a UX and engineering perspective
Include edge cases or accessibility considerations
Clarify how the story contributes to both experience and business outcomes
This format doesn’t replace visual design. It enhances it by anchoring decisions in shared goals.
When UX work is expressed through stories, it becomes embedded in the development process — not just handed off to it. And that shift can turn a good design into a well-executed product experience.
Embed UX in the Delivery Environment
One of the most common frictions in Agile teams isn’t resistance — it’s separation. Design lives in Figma. Research hides in Notion. Execution runs through Jira. Each space serves a purpose, but without integration, ideas get fragmented and momentum fades.
To work cross-functionally, UX thinking needs to live where decisions are made.
Project managers often use tools like Confluence as information radiators — centralized hubs where decision context and delivery rationale stay visible across teams. UX teams can extend this mindset across design, research, and development tools to reduce silos and keep momentum flowing.
Use Notion or Confluence to document design rationale, not just outcomes
Embed Figma links alongside customer interviews, journey maps, and Jira tickets
Create living briefs that evolve as the product does — instead of static PDFs forgotten after kickoff
Tag stories with research sources or experiment results directly in your backlog
This also supports Agile Principle #6: “The most efficient method of conveying information is face-to-face conversation.”
In distributed or hybrid teams, making work visible becomes the next best thing.
This is what makes UX operational: when ideas are not just presented but referenced, traced, and iterated across the delivery workflow.
The goal isn’t to duplicate everything. It’s to reduce friction. When research and design context travels with the task, teams don’t have to stop and ask why something matters — they already know.
In a collaborative environment, visibility is impact.
When UX Thinks Like a Project
Adopting a project management mindset doesn’t mean giving up your creative instincts or turning design into a checklist. It means borrowing just enough structure to make UX work more actionable — and more influential across the product lifecycle.
That includes:
Framing design problems around user and business outcomes
Prioritizing work based on confidence, constraints, and timing
Scoping ideas realistically with available capacity
Tracking progress in terms of results — not just deliverables
This isn’t about rigid process. It’s about clarity. When UX is scoped like an initiative and tracked like a product, it becomes easier to defend, easier to evolve, and easier to build on.
Structured workflows like the Now/Next/Later roadmap support this shift by helping teams focus on priorities without overcommitting to speculative features. They give just enough visibility to plan, while preserving the flexibility to adapt.
Structure doesn’t dilute creativity — it provides a shared frame of reference that helps teams stay aligned as they solve complex problems. When UX work is grounded in intent and supported by lightweight delivery practices, it becomes easier to prioritize, easier to communicate, and easier to scale.
Thinking like a project manager doesn’t mean losing the soul of design. It means treating design as essential to delivery — not adjacent to it. And when UX leads with clarity, alignment, and purpose, it doesn’t just support the product. It shapes how the product works, feels, and evolves over time.
That’s not a loss of creativity — that’s design maturity.
Design is more powerful when it’s not just aesthetic, but operational.