Link copied to clipboard
.jpg)
A few years ago, a client hired me for what looked like a straightforward design project. They asked me to fly to their office so we could work closely together, and from the outside it sounded simple: the team believed they understood their user and the problem they needed to solve.
On paper, it looked aligned.
But once we got into the work, the “alignment” was mostly assumed, not real. The CEO and the other co-founder had different ideas about what the product needed to be. Their internal lead designer had another opinion entirely. And suddenly, instead of making decisions based on the user’s needs, the project started drifting into competing preferences.
That’s when I pushed to pause and get everyone in a room to clarify the fundamentals: who we were building for, what we were solving, and what success would look like. That’s always my role, not to pick sides, but to protect the user and keep the work anchored in their reality rather than internal politics.
The project moved forward after that, but it took longer than it should have. Not because the design was hard, but because the team hadn’t agreed on the problem they were solving.
In femtech, this gets even more expensive. These products rely heavily on trust. Users are sharing sensitive information about their bodies, their health, and their lives. That kind of trust is not built through isolated design decisions. It comes from a consistent, coordinated experience across product, marketing, and customer support. When the team behind the product is misaligned, that consistency breaks down fast.
Designers can solve complex problems, but they cannot solve problems your team has not agreed on.
When a team is unclear about the goal of a project, the designer is forced to make assumptions. For example, are you trying to improve conversion? Educate users about a complex health topic? Reduce friction during onboarding? Each of these goals leads to very different design decisions.
If the team has not aligned on the priority, the designer ends up working in a vacuum. The work might be thoughtful and well executed, but it is built on unstable ground.
Misalignment also creates what many designers quietly call “design by committee.” Feedback starts coming from multiple directions, often with completely different priorities behind it. One stakeholder wants to simplify the interface to improve usability. Another wants to add more information for credibility. Someone else is worried about investor perception and pushes for something that feels more “impressive.”
None of these perspectives are inherently wrong. The problem is that they are rarely aligned.
When this happens, designers are pulled into cycles of conflicting revisions. Each round of feedback nudges the work in a different direction, and over time the original clarity of the design gets diluted. Instead of solving the user’s problem more effectively, the product becomes a compromise between internal opinions.
Even when the design itself is strong, misalignment often shows up later during implementation. Product, marketing, and engineering teams may interpret the same designs differently because they are optimizing for different outcomes. What ships ends up inconsistent across touchpoints, and the user experiences that fragmentation immediately.
The cost is not just aesthetic. It is time, money, and momentum. Projects drag on longer than expected. Revision cycles multiply. And sometimes the most painful outcome happens quietly: thoughtful design work sits unfinished or unused because the team cannot agree on how to move forward.
Alignment does not mean everyone agrees on every detail. Startups move too fast for that.
What it does mean is that the team shares clarity on a few core decisions before design work begins.
First, everyone should be able to answer the same question the same way: who are we building for and what is their biggest problem? If you ask three people on the team and get three different answers, the project is not ready for design yet.
In femtech, this question is particularly important because users are navigating complex, personal experiences. Pregnancy, fertility, hormonal health, postpartum recovery, menopause. These are not abstract problems. They are lived realities, often with emotional and medical dimensions. If the team does not share a clear understanding of the user’s primary need, the product experience will quickly become fragmented.
Alignment also means agreeing on how the product builds trust.
Trust can come from many places. Clear medical credibility. Transparent explanations. Privacy protections. Empathetic language. Some products prioritize education. Others focus on simplicity and emotional reassurance. None of these approaches are inherently right or wrong, but the team needs to decide which signals matter most for their users.
Without that clarity, design decisions become reactive. Every screen becomes a debate instead of a step toward a shared goal.
Finally, strong alignment requires clear decision-making authority. Someone needs to have the final say on design direction. Not to override the team, but to prevent endless cycles of feedback and revisions.
When these foundations are in place, designers can do their best work. Instead of navigating internal disagreement, they can focus on what actually matters: creating an experience that solves the user’s problem clearly, consistently, and with care.
Alignment does not require a three-day offsite or a complicated framework. In most early-stage startups, a focused conversation with the right people is enough.
Ideally, teams have this clarity before bringing a designer into the project. But in practice, many founders bring in a designer specifically to help facilitate that alignment.
One approach is to run a short internal alignment session with the key stakeholders. Typically this includes the founders, product lead, and anyone responsible for marketing or growth. The goal is simple: define who the core user is, what problem you are solving for them right now, and what success for this project would look like.
Another option is to involve your designer directly in this process. In many of my projects, the first step is a scoping or strategy session where we work through these questions together. Instead of jumping straight into screens, we clarify the user, the core problem, and the priorities for the design work. This ensures that the design decisions that follow are grounded in shared understanding rather than assumptions.
Once those decisions are made, it helps to document them. This does not need to be a long strategy document. A short brief is usually enough. Write down the user you are prioritizing, the key journey you want to improve, the trust signals that matter most, and the metric that will tell you whether the work succeeded.
Finally, clarify decision-making authority. Someone should have the final say on design direction and trade-offs. Without that clarity, feedback loops can stretch endlessly as different stakeholders push the work in different directions.
When this kind of alignment happens early, the design process becomes dramatically smoother. Instead of debating fundamentals, the team and the designer can focus their energy on what actually matters: building a product experience that genuinely helps the user.
If you are already working with a designer and the project feels stuck, it is worth pausing for a moment before assuming the issue is the design work itself.
Often what looks like a design problem is actually internal disagreement surfacing through design feedback. Different stakeholders may be reacting to the same screens with completely different expectations about the product, the user, or the goal of the project.
When that happens, continuing to iterate on the design rarely solves the underlying issue.
A better approach is to step back and have a short alignment conversation with the team before the next design review. Revisit the same fundamentals: who the core user is, what problem you are solving right now, and what success for this project actually means.
Once the team agrees on those points, share that clarity with your designer. Designers do their best work when they are not caught between competing internal perspectives. When the direction is clear, they can focus on translating that shared vision into an experience that works for the user.
Sometimes a short pause to realign can save weeks of revisions and frustration later.
In many products, inconsistent design is mostly an inconvenience. In femtech, it can undermine trust.
These products often ask users to share deeply personal information about their bodies, their health, and their life stages. Fertility, pregnancy, hormonal health, postpartum recovery, menopause. These are sensitive, emotional experiences where users are already navigating uncertainty.
When a product feels fragmented or inconsistent, people notice immediately.
If the marketing promises one experience but the product feels different, trust weakens. If the onboarding flow says one thing and the interface communicates another, users start questioning whether the product truly understands them. And if the overall experience feels disjointed, people may assume the company behind it does not fully understand their needs.
That is why alignment inside the team matters so much.
Design can amplify a clear vision. It can translate shared understanding into an experience that feels intuitive, supportive, and credible. But design cannot create that alignment on its own.
Before design work begins, make sure your team agrees on the fundamentals. Who the user is. What problem you are solving. And what success for this project actually looks like.
When that clarity exists, design becomes far more powerful. Not because the screens look better, but because every part of the experience is working toward the same goal: helping the user feel understood, supported, and confident using your product.
If your team needs help getting aligned on what to focus on, you can contact me here to set up a scoping session.
