Proactive by Design
Redefining Initiative through a Projector’s Lens
For years, I’ve worked at the intersection of design, leadership, and mentorship—guiding teams through complex product decisions and helping individuals grow into their potential. As a design manager, I’ve had to cultivate not just craft, but presence. Yet during a recent chapter of my career, as I returned to an individual contributor role, I began to reflect more deeply on what proactivity really means for someone like me: a thoughtful, observant designer who identifies with the Human Design profile of a Projector.
Projectors aren’t wired to charge ahead blindly or to outpace others by sheer energy. We lead by seeing. We influence not through noise, but through clarity. So when I received direct feedback to be more “proactive” at work—more vocal in critique, more challenging of assumptions, more willing to push—I found myself grappling with how to do that authentically. Not just to meet expectations, but to honor how I’m built to contribute.
That exploration has led me to rethink the idea of proactivity in UX and product design—not as a performance, but as a deliberate and strategic practice. In this article, I want to unpack what being proactive can look like for designers, especially those who don't identify as loud or dominant voices in the room. What does it mean to step forward with intention? How can we challenge confidently, without becoming combative? And how can we transform quiet observation into tangible impact?
Rethinking Proactivity in Product Design
In many product teams, proactivity is often equated with speed or dominance: the designer who jumps into Figma first, speaks up earliest in meetings, or makes fast calls on layout decisions. But these signals can be misleading. Proactivity isn't just about being the first to act—it's about acting with foresight.
A proactive designer doesn’t just respond to tickets. They investigate upstream. They ask: Why this feature now? What problem are we truly solving? Is the user story fully considered? And is there a better way to frame the entire flow?
Unfortunately, in fast-moving environments, the pressure to "keep up" often overrides these deeper inquiries. Teams may prioritize delivery over depth, leading to the very patterns many of us try to avoid: patchwork UX, reactive redesigns, and missed user expectations. Ironically, a proactive designer in this environment may not always look like they’re moving fast—because they’re pausing to examine what’s being overlooked.
The PRD Isn’t Sacred—It’s a Conversation Starter
One of the most useful places to practice proactive thinking is in how we approach the Product Requirements Document (PRD). Too often, designers treat the PRD as a fixed blueprint: something to execute rather than interrogate.
But the PRD, especially in iterative product teams, is rarely perfect. Assumptions sneak in. Edge cases are left out. UX decisions get implied, not stated. Waiting until design handoff to discover these gaps only creates frustration—and puts the burden of course correction on the tail end of the process.
A more proactive approach is to treat the PRD as a living artifact. Before jumping into screens, proactive designers will map out what feels unclear, challenge weak assumptions, and raise the types of questions that anticipate downstream pain:
What’s the real user context here?
Have we accounted for all user types?
How will this experience scale or break?
This doesn’t have to be confrontational. In fact, when framed as curiosity rather than critique, these conversations earn trust. Proactive designers aren’t pushing back to resist—they’re pushing forward to refine.
The Power of Pre-Design Reflection
Designers are often praised for their execution: beautiful UIs, interactive prototypes, smooth animations. But execution without reflection can be shortsighted. Proactive design begins before pixels.
One practice I’ve adopted is to write a short “design intention memo” before starting any design work. It includes my understanding of the feature, assumptions I’m questioning, opportunities to elevate the user experience, and what support I need to move forward.
This simple ritual does two things: it gives product stakeholders a window into my thought process, and it creates a shared alignment before execution begins. Instead of waiting until critique to surface deeper insights, I bring them upfront—when there’s still time to influence direction.
In teams where product managers are moving quickly, this approach helps establish design as a strategic partner, not a passive executor.
Leading by Guidance, Not Volume
If you’re a designer who doesn’t always speak first in meetings, that doesn’t mean you lack initiative. Some of the most impactful contributions come not from dominating the room, but from saying the right thing at the right time.
Projectors in Human Design are wired to guide. They see the system—the patterns behind the patterns. In modern UX work, this often shows up as the ability to connect user behavior, business constraints, and technical implications into a holistic view.
Instead of fighting to be the loudest voice, proactive designers can lead by:
Creating short internal insights reports on patterns seen across user testing
Proposing small but meaningful upgrades to a journey map or onboarding flow
Initiating design reviews not to showcase progress, but to uncover what’s still missing
True influence doesn't always look dramatic. Sometimes, it looks like subtle course correction that saves the team weeks of wasted effort.
Invitation ≠ Invisibility
One of the most misunderstood aspects of being a thoughtful, guiding designer is the idea that you have to wait to be asked. But in reality, you can create the conditions for the invitation.
Share your thought process early. Make your insights visible. Invite others into your analysis—not to prove you’re right, but to show you're invested.
You might:
Invite PMs to a short "PRD audit" before design begins
Send a Zoom walkthrough of your Figma file, not just for feedback, but to ask “what else are we not seeing?”
These gestures aren’t about ego. They’re about creating pull rather than push. And over time, they position you as someone whose insights are not only valued—but sought out.
Balancing Presence with Energy
One of the traps proactive designers fall into is overextending—especially when trying to meet expectations that feel misaligned with how they naturally work. Proactivity should not lead to burnout.
It’s essential to be selective. Choose the right projects to go deep on. Protect your time to reflect. And say no to tasks that dilute your value.
The most effective proactive designers don’t try to do it all. They identify high-leverage moments, shape them with intention, and let their presence ripple outward.
A Reflection to Consider
If you’ve ever been told to "speak up more," "be more aggressive," or "challenge the team," take a step back and ask yourself:
What would proactivity look like if it honored both my personality and my purpose?
Being proactive doesn’t mean becoming someone you’re not. It means knowing what you see, trusting that it’s valuable, and choosing the most meaningful moments to share it.
Closing Thought
Proactivity in design is not about volume, speed, or bravado. It’s about vision, timing, and care. Whether you're wired like a Projector or simply prefer reflection over reaction, there is a path to being influential without burning out.
In today’s product environments, teams don’t just need fast execution—they need thoughtful navigation. And that’s where proactive designers, working in alignment with who they truly are, can create their greatest impact.