How Experience Has Shaped the Way We Approach UX, Collaboration, and Product Design
The way a UX team works doesn’t stay the same forever. Every project brings new perspectives, challenges, and opportunities to improve. At Pepperplane, experience has shaped how we approach discovery, collaborate with developers, share unfinished work, and make product decisions. Here’s a closer look at the thinking behind our process today and why we believe there’s always room to keep learning.
If you looked at how a UX team worked a few years ago and compared it with how they work today, you’d probably notice a few differences. Not necessarily in the tools they use or the types of projects they take on, but in the smaller decisions that shape how the work gets done.
Maybe they ask different questions during discovery. Maybe they’re more comfortable sharing an idea before it looks presentable or perhaps they’ve learned that a conversation with a developer early in the process can be more useful than a perfectly documented handoff later. These changes rarely happen overnight. They tend to develop through experience, one project and one conversation at a time.
At Pepperplane, we believe the work should change the way we work. Every project is an opportunity to learn something about our process, our collaboration, and how we can better support the teams we partner with and sometimes, the most valuable lessons aren’t about the final design at all.
We've Learned to Spend More Time Understanding Before Moving Into Solutions
There’s a natural excitement that comes with starting a new project. A client has a challenge to solve, the team has ideas, and everyone is eager to start exploring what the solution could look like. That enthusiasm is a good thing. But experience has reinforced the importance of making sure we’re solving the right problem before getting too attached to a particular direction.
It’s easy for a conversation to move quickly from “Here’s the challenge we’re facing” to “Here’s what we think we should build.” The space between those two statements is where a lot of valuable UX work happens.
Today, we place real importance on discovery conversations, workshops, user research, and mapping exercises that help us understand the context behind a request.
We’re interested in what users are trying to accomplish, what the business needs to achieve, and which assumptions might be influencing the proposed solution.
The goal isn’t to slow down the project. It’s to create enough clarity that the team can move forward with greater confidence.
Sometimes the discovery process confirms the direction everyone had in mind. Other times, it reveals a different opportunity or helps the team reconsider something they initially thought was essential. Either way, the thinking that happens before design gives the work a stronger foundation.
We're More Comfortable Showing Work That Isn't Finished
There’s something satisfying about presenting a polished design. Everything looks considered, the interactions feel complete, and the idea is much easier for people to imagine as a finished product. But we’ve come to appreciate the value of showing the work before it reaches that stage.
An early sketch or wireframe creates a different kind of conversation. Instead of focusing on colours, spacing, or visual details, the team can discuss how the experience should work, whether the proposed flow makes sense, and what might still be missing.
It also makes changing direction feel like a natural part of the process rather than something that needs to be justified. That’s why Design Reviews are such an important part of how we approach collaboration.
We want people to question the thinking, challenge assumptions, and share perspectives while those conversations can still influence the solution. And yes, sometimes that means revisiting an idea we were initially quite happy with.
We’ve learned that unfinished work isn’t something to protect from feedback. It’s often where feedback can be most valuable. The sooner we can bring people into the thinking, the more opportunities we have to improve it together.
Developer Conversations Have Become Part of the Design Conversation
One of the things we value in our process today is the opportunity to collaborate with developers before a design reaches the handoff stage. Developers bring a perspective that can challenge and strengthen the work in ways that aren’t always obvious when we’re focused on the interface. They understand technical dependencies, existing systems, implementation considerations, and the scenarios that need to be accounted for when a design becomes a working product. Sometimes a developer asks a question that reveals an edge case nobody has fully explored. Other times, a technical constraint leads to a simpler approach that works just as well, or even better, for the user.
These conversations have reinforced something important for us: the strongest product decisions often come from bringing different perspectives together before the solution feels final. That doesn’t mean every technical detail needs to be resolved during early design. It means recognising when involving developers can help the team make a better-informed decision. Rather than seeing handoff as the moment collaboration begins, we see it as one point in a much longer conversation. And the more context everyone shares throughout that conversation, the easier it becomes to understand not just what needs to be built, but why.
We're Paying More Attention to the Thinking Behind Decisions
A lot of important decisions happen during a UX project, and not all of them are obvious when someone looks at the final design. A particular flow might have been chosen because of user feedback. An interaction could have changed after a Design Review. A feature might have been simplified because the original approach introduced unnecessary complexity. At the time, everyone involved usually understands the reasoning. But as the project moves forward, that context can become harder to find. We’ve come to value keeping the why behind important decisions visible, whether that’s through workshop notes, annotations, Figma comments, or conversations documented for the wider team. This isn’t about recording every discussion or creating more documentation for the sake of it. It’s about making sure the thinking doesn’t disappear once the team moves on to the next task.
A design decision becomes much more useful when the people working with it understand the reasoning behind it. That context helps developers implement the experience with greater confidence, makes it easier for stakeholders to understand the direction, and gives the team a clearer starting point when something needs to be revisited. Sometimes a short note can save a surprisingly long conversation later. And if there’s one thing most product teams can appreciate, it’s avoiding a meeting that could have been prevented by a well-placed comment.
Experience Has Made Us More Comfortable With Changing Our Minds
Perhaps one of the most valuable things that comes with experience is becoming more comfortable with the idea that the first solution won’t always be the right one. An early concept might look promising until research reveals something unexpected. A user flow might need to change after the team explores an overlooked scenario. Or feedback might introduce a perspective that makes everyone reconsider the original approach. It’s tempting to see these moments as interruptions to progress. But we’ve learned that changing direction because you’ve learned something new is different from changing direction because the team doesn’t know what it’s doing.
Good UX requires room for exploration, testing, and reconsideration. That doesn’t mean constantly revisiting every decision or allowing a project to move without clear direction. It means creating a process where new information can influence the work when it genuinely improves the outcome. And sometimes, the most useful thing we can do is step away from an idea we were excited about because the team has discovered a better way forward.
The final product might never show how many alternatives were explored or how much thinking went into a particular decision. But those conversations are part of what makes the experience stronger.
What This Means for the Teams We Work With
The way we approach UX today reflects what we value in a partnership. We want to understand the problem before jumping into solutions. We want stakeholders and developers to feel involved in the thinking, not simply brought in to approve or implement decisions. And we want feedback to be part of how the work develops, rather than something that happens only when a design looks finished.
For our clients, that means working with a UX team that values transparency, shared understanding, and open communication throughout the process. It also means recognising that no two projects need exactly the same approach. Some teams need help creating clarity around an early product idea. Others have established products and development teams but need additional UX expertise to improve an existing experience.
Our role is to understand where we can add the most value and adapt the way we work to support the people and product in front of us. We don’t believe a good UX partnership is about arriving with every answer. It’s about bringing the right experience, asking thoughtful questions, and working together to find the best way forward. And the more we learn from the projects we work on, the better we can continue to do that.
Final Thought
One of the things we appreciate about UX is that there’s always something new to learn. Sometimes it’s a better way to approach discovery. Sometimes it’s a small change to how we collaborate with developers. And sometimes it’s realising that a question we now ask automatically is one we wouldn’t have thought to ask a few projects ago. Those changes might not seem particularly significant on their own, but over time, they shape the way a team thinks, communicates, and makes decisions.
Experience doesn’t mean we’ve reached a point where our process no longer needs to change. It means we’re better equipped to recognise when it should. And that’s something we want to keep carrying into every project we take on.
Ready to Build Better Products Together?
Looking for a UX partner who brings experience, collaboration, and thoughtful problem-solving to your next project? We’d love to learn more about what you’re working on and explore how we can help.