A few lessons from real projects that can make the entire process smoother
Every product team wants a smoother project, fewer surprises, and a better end result. But some of the decisions that make the biggest difference happen before the first screen is designed. From involving UX earlier to bringing developers into the conversation and getting comfortable with imperfect requirements, we’re sharing a few lessons we’ve learned about setting product teams up for success.
Every project starts somewhere. Sometimes it’s a new product idea, sometimes it’s a feature that needs improving, and sometimes it’s an existing platform that’s become a little more complicated than anyone originally intended. Over the years, we’ve worked alongside product teams, developers, stakeholders, and businesses at different stages of their product journeys. And while every project comes with its own challenges, we’ve noticed that some of the things that make UX projects run more smoothly have very little to do with the actual design work.
They have more to do with when conversations happen, who’s involved, what everyone understands about the problem, and how comfortable the team is with figuring things out together. Looking back at different projects, there are a few lessons we find ourselves returning to. Not because there’s one perfect way to approach UX, but because we’ve seen how much easier the process becomes when certain things are considered from the beginning. So, if you’re about to start a UX project, or even thinking about bringing a UX partner into an existing one, here are a few things we’d love every product team to know.
1. Bring UX in before all the important decisions have been made
One of the most common misconceptions about UX is that it becomes relevant once the product requirements are finalised and the team is ready to start designing screens. But by that point, some of the most important product decisions may already have been made. The features have been agreed upon, the scope has been outlined, and everyone has a fairly clear picture of what they expect the solution to look like. The challenge is that UX can add the most value when there’s still room to question those decisions.
When UX is involved earlier, there’s an opportunity to explore the problem before committing to a particular solution. We can better understand what users are trying to accomplish, identify assumptions that need validating, and work with the team to determine which parts of the experience actually need attention. Sometimes that confirms the direction everyone was already considering. Other times, it reveals a simpler approach or highlights something the team hadn’t thought about yet. We’ve learned that bringing UX in early doesn’t necessarily mean adding more time to a project. It means giving the team an opportunity to make better-informed decisions before those decisions become more difficult to change.
And while earlier is usually better, there’s never a wrong time to start improving the user experience. Even when a product is already live or development is underway, UX can help teams reassess priorities, uncover friction, and identify opportunities to make the experience better.
2. Get everyone aligned on the problem before designing the solution
It’s entirely possible for everyone in a meeting to agree on what needs to be built while having slightly different understandings of why they’re building it. The client might be focused on a business goal. The product owner might be thinking about functionality and deadlines. Developers might already be considering technical requirements, while designers are thinking about how the experience should work for users. None of those perspectives is wrong. In fact, they’re all important. But when those perspectives aren’t brought together early, misalignment can quietly make its way into the work.
That’s why we place so much value on the conversations that happen before design begins. Workshops, stakeholder discussions, user research, journey mapping, and user story mapping give teams an opportunity to build a shared understanding of the problem. They help clarify what success should look like, where the biggest challenges are, and which questions still need answering. We’ve seen how valuable it can be when someone asks a seemingly simple question during one of these conversations and the team realises they’ve been approaching the problem from different angles. Those moments aren’t setbacks. They’re often exactly why the conversation needed to happen.
Alignment doesn’t mean everyone has to agree on every detail. It means everyone understands what they’re trying to achieve and why it matters. And when that understanding is established early, the decisions that follow tend to become much clearer.
3. Developers should be part of the conversation earlier
There’s a familiar version of the product development process where designers complete their work, prepare the files, and then hand everything over to developers. In theory, it sounds straightforward. In practice, some of the most valuable conversations happen when designers and developers start working together long before that handoff.
Developers bring an entirely different perspective to the work. They understand technical dependencies, implementation challenges, existing system constraints, and the things that might become complicated once a design moves beyond Figma. And sometimes, one question from a developer can reveal something important that hasn’t been fully considered. What happens when there’s no data to display? How should this interaction behave on a smaller screen? Does this new feature need to work with an existing system? Is there a simpler way to achieve the same outcome? These questions aren’t just about making development easier. They can make the user experience better too.
One of the lessons we keep coming back to is that involving developers earlier creates more opportunities to solve problems collaboratively, rather than discovering them when the design is already considered finished. It also gives designers a better understanding of what’s technically possible and gives developers more context about the reasoning behind particular design decisions. At Pepperplane, we see design and development as part of the same product conversation. The strongest outcomes tend to happen when everyone has the opportunity to contribute their expertise while there’s still room to explore different solutions.
4. You don't need perfect requirements to start the conversation
We’ve worked with teams at different stages of clarity. Some arrive with detailed documentation, established requirements, and a well-defined roadmap. Others have a problem they know needs solving, a few ideas about how to approach it, and a long list of questions. Both are perfectly reasonable starting points.
One thing we’d love more product teams to understand is that you don’t need to have everything figured out before involving UX. In fact, helping teams work through uncertainty is an important part of the UX process. A conversation that starts with “We’re not entirely sure how this should work” can lead to some of the most useful discovery work. It gives us an opportunity to explore what’s known, identify what’s still unclear, and understand what information is needed to move forward.
Of course, having requirements and documentation is helpful. But waiting until every detail feels complete can sometimes mean delaying conversations that would have helped shape those requirements in the first place. And there’s another thing we’ve learned: even the most carefully prepared requirements can change once a team starts speaking to users, testing assumptions, or exploring the experience in more detail. That’s not necessarily a sign that something has gone wrong. It can be a sign that the team is learning. The goal isn’t to start with every answer. It’s to start asking the right questions.
5. Make room for feedback before the work feels finished
There’s something satisfying about presenting a polished design. Everything looks considered, the interactions feel complete, and the team can finally see the product taking shape. But we’ve learned that some of the most valuable feedback happens well before that point.
Early sketches, rough wireframes, user flows, and unfinished concepts give people an opportunity to focus on the thinking behind a solution rather than getting distracted by the visual details. They also make it easier to challenge an idea without feeling like the team is undoing hours of finished work.
This is one of the reasons we value Design Reviews throughout the process. They’re an opportunity to ask questions, test assumptions, explore alternatives, and bring different perspectives into the work while those perspectives can still influence the outcome.
And yes, sometimes a Design Review leads to changing something we were quite happy with five minutes earlier. That’s part of the process. Feedback is most useful when there’s still room to do something with it. We’ve found that teams benefit when unfinished work is treated as something worth discussing, rather than something that needs to be hidden until it’s ready for approval. It creates a more collaborative environment and helps everyone stay involved in shaping the solution.
6. Not every problem needs another feature
When a team identifies a problem, the natural response is often to think about what needs to be added: a new feature, another screen, an extra step in the workflow, or more functionality to give users additional options. Sometimes that’s exactly what’s needed, but not always.
We’ve learned that improving a product can be just as much about simplifying the experience as it is about adding to it. A confusing workflow might not need another feature – it might need fewer steps. An interface that feels overwhelming might not need more information – it might need clearer priorities. A user who keeps getting stuck might not need additional instructions – the experience itself might need to become more intuitive.
This is where understanding the underlying problem becomes particularly important. Rather than jumping straight to what could be built, we try to explore what users are actually struggling with and what would make their experience easier. Sometimes the most useful design decision is choosing not to add something at all. And for product teams balancing user needs, business priorities, development effort, and delivery timelines, that can be a valuable outcome in itself.
7. The best project processes leave room for learning
It’s tempting to think that a successful UX project is one where everything goes according to the original plan. The requirements are clear, the timeline stays exactly as expected, every decision is made quickly, and the first design direction works beautifully. That would certainly make project management easier. But real product work rarely unfolds quite so neatly.
New information comes up. Users challenge assumptions. Technical considerations change how something needs to work. Stakeholders bring new context into the conversation, and sometimes a solution that looked promising at the beginning turns out not to be the right one.
We’ve learned that a good process shouldn’t try to eliminate every possible change. It should create enough structure to keep the team moving while leaving room to respond to what the team learns.
That means being clear about goals and priorities, documenting important decisions, involving the right people at the right time, and making sure everyone understands when and why a direction changes. It also means recognising that progress doesn’t always look like moving straight from one deliverable to the next.
Sometimes progress is identifying an assumption that needs testing. Sometimes it’s simplifying a complicated user flow. And sometimes it’s deciding to revisit an idea before investing more time in building it. Those decisions might not always be visible in the finished product, but they can make a meaningful difference to how confidently the team moves forward.
What this looks like at Pepperplane
At Pepperplane, we approach UX as a collaborative process rather than something that happens separately from the rest of the product team.
We want to understand the business goals, the people using the product, the technical environment, and the challenges the team is working through. We use discovery conversations, workshops, research, mapping, and early design exploration to help create clarity before moving into more detailed design work.
We also believe in bringing different perspectives into the process. That includes working closely with stakeholders, collaborating with developers, and using Design Reviews to question assumptions and improve ideas before they become final decisions.
Of course, every project is different. The level of discovery, the people involved, and the way we structure the work will depend on what the product and team actually need.
But the principle remains the same: good UX isn’t something we deliver to a product team. It’s something we help create together. And the earlier we can start those conversations, the more opportunities we have to shape the right solution.
Final Thought
If there’s one thing we’d love every product team to take away from these lessons, it’s that you don’t need to have everything figured out before starting UX. You just need to be willing to figure things out together.
The most productive projects aren’t necessarily the ones that begin with the most detailed requirements or the clearest picture of the final product. They’re often the ones where people are willing to ask questions, share what they know, challenge assumptions, and stay open to learning along the way. Because a smoother UX process doesn’t come from avoiding every difficult conversation or unexpected discovery. It comes from creating the kind of collaboration where those moments help move the work forward. And if we can help teams do more of that from the beginning, we’re already off to a pretty good start.
Ready to Build Better Products Together?
Whether you’re exploring a new product idea, preparing for development, or looking to improve an existing experience, we’d love to be part of the conversation. Let’s talk about how UX can help your team move forward with greater clarity and confidence.