More than once, I’ve been asked to update and “show my project progress”. I get it, in most people’s minds, visual elements equal progress. But in UX design, the most valuable work often happens before there’s anything to see. Some days, the progress is invisible: early alignment conversations, feasibility checks with engineers, or scope negotiations that quietly prevent weeks of rework. And here’s the irony: this quiet, strategic work is the reason projects run smoothly, yet in daily updates or creative reviews, it’s often overshadowed by how things look.
“Much of my work is invisible—but that doesn’t mean it’s not valuable.”
That’s the trap: when progress is measured only in visible pixels, the strategic work that actually makes design successful gets overlooked, and that’s when projects start to break.
The Core Problem
When a company treats UX as something you “add on” at the end, design becomes a race to produce pretty screens instead of a process for solving problems. The pressure to show something, anything, often pushes designers straight into high-fidelity mocku ps. I’ve even encountered situations where engineering teams make the first effort with clickable propotypes just to get something visible in front of stakeholders. That movement may look like progress, but it can be misleading. If the strategy isn’t clear, the goals aren’t aligned, the needs haven’t been discussed, and the constraints aren’t understood, every pixel you design is a gamble. I’ve seen it happen over and over:
- Misaligned goals make the team design for different success metrics or a double effort in different departments that create more confusion and extra work.
- No early feasibility checks means beautiful concepts collapse when engineering reality hits.
- Lack of scope negotiation shrinks timelines while expectations grow.
The result? Rework. Delays. Frustration. And ironically, less trust in the design process, because to the outside world, it looks like design “wasted time.” We already had the product, we just needed to make it look good. The truth is, the most strategic work in UX often has no interface at all. It happens in the conversations, decisions, and trade-offs you make before opening Figma. That’s the work that keeps projects on track… and the work that too often goes unseen.
UX as the Choreographer, Not Just the Artist
UX isn’t just about producing a design, it’s about orchestrating how business goals, user needs, and technical constraints come together to create something that actually works. That orchestration is less like painting a picture and more like choreographing a performance. Each discipline - product, design, engineering - has its own timing, style, and priorities. Without a shared rhythm, you get missteps, awkward pauses, or entire sequences that fall apart. The designer’s role in this isn’t simply to “add beauty” at the end. It’s to:
- Set a shared understanding of the goal before the first step.
- Align the tempo so teams know when to move fast and when to pause.
- Coordinate interactions between disciplines so they complement each other instead of colliding.
This may sound like the PM’s job, and in many ways, the two roles overlap in coordinating work. But they are not the same. PMs focus on what gets built and when, managing timelines, priorities, and resources. Designers focus on how the product comes together and why it matters, ensuring that the experience is meaningful, usable, and feasible. When this choreography happens early, design stops being the last checkpoint before launch, and becomes the central thread that holds the project together. And here’s the kicker: this is the work that most people don’t see… until it’s missing. That’s when you notice the misalignments, the missed handoffs, the features that looked good in Figma but never made it into production.
The Invisible Work in Action – 4 Core Areas
Ok, cool, this sounds great, but what to do with this information? Well, here are four areas where this invisible work plays out, with real examples I’ve seen or lived:
- Early Alignment Before jumping into design, I make sure everyone’s on the same page about goals, working styles, and constraints. For example, asking about time zones, preferred work hours, or whether the team prefers detailed specs or lightweight prototypes helps avoid misunderstandings down the line.
- Negotiating Scope and Timelines Saying “yes” to everything might seem easier, but it often leads to burnout and poor quality. I’ve learned to push back when deadlines or scope don’t make sense, using clear communication to reset expectations and protect the team’s bandwidth.
- Cross-Functional Feasibility Including engineers early to understand technical constraints saves redesign later. Without this, I’ve seen great ideas fall apart because they were impossible or prohibitively expensive to build. And yes, it’s frustrating to have an idea denied, but it’s much better to find out early than after months of work.
- Deliverables That Work for Others Instead of assuming Figma files are the one-size-fits-all deliverable, I ask engineers how they prefer to receive specs—whether that’s in Figma, slide decks, or spreadsheets. This small adjustment speeds up implementation, reduces frustration, and cuts down on back-and-forth questions about projects you’ve already mentally closed.
Why This Work is Invisible and Why It’s Essential
This work doesn’t create daily “pretty updates,” so it’s often undervalued.But it’s the multiplier for speed, quality, and collaboration. This invisible work of UX isn’t just about keeping projects on track, it’s about shaping how teams think and collaborate. As products grow more complex and technologies evolve, it’s no longer enough to design isolated screens. We need to design adaptable experiences that work across devices, cultures, and contexts. And that starts with the conversations and alignments that most people don’t see. This is where UX moves from being a role to becoming a strategic force, the glue that holds together business goals, user needs, and technical realities.
What If We Valued the Invisible?
What happens when early conversations, feasibility checks, and scope negotiations were seen as milestones, not just “nice-to-haves.” When designers were trusted to lead these discussions, not just execute visual tasks. And when the success of UX was measured not by how fast you ship pixels, but by how well you set the stage for everything that follows. That’s the future I want to help build. And with AI reshaping workflows, it’s becoming more real every day. But it starts with recognizing that the invisible work is the real work. If we start treating this alignment as design work, not just overhead, we unlock a completely different way of working. Next time you start a project, spend your first days not in Figma, but in conversations. Start by asking:
- What are our working constraints?
- How will we collaborate?
- How will decisions be made?
- What format is best for handoff?
Because maybe the real mark of a senior designer isn’t how fast they can produce designs but how well they can align a team before a single pixel is placed.
