The Frame That Shapes Your Influence

I have been spending time mentoring designers through ADPList. The sessions are structured around interview preparation, portfolio review, and career strategy. What I keep noticing is not about the craft. It is about how designers describe what they do.

The designers who land senior roles and earn influence inside their organizations are rarely the ones with the most polished screens or the most research hours. They are the ones who frame their work differently. The way they talk about their past projects reveals an operating model that is already oriented toward outcomes — even if they do not use that language yet.

The gap I see most often is not in the quality of the work. It is in the story the designer tells about it.

Two Versions of the Same Project

I have heard versions of the same project described two completely different ways.

Version one: "I redesigned the onboarding flow. I did user research, created wireframes, iterated based on feedback, and delivered high-fidelity screens. The team implemented it and the metrics improved."

Version two: "We had a problem where 40% of new users were dropping off by step three. The team assumed it was a motivation issue — users did not understand the value. I talked to users and found it was actually a confusion issue. They did not know what to do next. That changed our approach. Instead of adding more explanatory copy, we removed two steps and restructured the flow around a single decision per screen. Engineering was able to ship it in half the time because we reduced the scope of what needed to be built. Drop-off went from 40% to 12%."

Both describe the same outcome. The second one gets the designer hired for a senior role — and more importantly, it reflects an operating model that earns influence on any team.

The difference is not that one version is more detailed. It is that the second version reveals the designer's relationship to the team, the business, and the problem. It shows the designer making judgments, not just executing steps.

The Frame Reveals Your Operating Model

I keep landing in the same place. How you talk about your work is not a communication technique. It is a signal of how you actually work.

A designer who describes a project as "I delivered screens" probably works in a handoff model. They receive requirements and produce output. That is fine for junior roles. It is a limitation at senior levels because the operating model itself is centered on production, not decision-making.

A designer who describes a project as "We realized X, so we chose Y" is describing a different operating model. They were present when the team made decisions. They understood the constraint well enough to navigate tradeoffs. They shaped what got built, not just what it looked like.

The frame is not something you add after the work is done. It is the structure you bring to the work itself. If you cannot answer the question "What did the team learn from your involvement?" from your last project, the problem is not that your portfolio needs better copy. The problem is that your operating model may not be producing the kind of contribution that earns influence.

Three Shifts That Matter

I keep seeing three frame shifts that separate designers whose influence grows from those whose influence stalls.

From delivery to decision

The most common frame I hear is delivery-oriented. "I designed the dashboard. I created the component library. I shipped the redesign."

The useful frame is decision-oriented. "The team needed to decide how to surface the most critical information without overwhelming clinicians. We tested three approaches and found that a tiered layout reduced cognitive load by 30% compared to a flat grid."

The first version says you can produce screens. The second says you can help the team make better decisions. Those are different capabilities, and organizations pay for the second one.

From volume to learning

I have reviewed portfolios where every project involves research, and the research is always followed by deliverables. The story is linear: discover, design, deliver.

The more useful frame includes what changed based on what the team learned. "We started with one approach. After user testing, we realized the mental model was wrong. We pivoted." Or "The research showed our initial assumption was incorrect, so we shifted the focus from feature X to integration Y."

A designer who shows adaptability to learning is describing someone who treats design as an investigation, not a production line. That is the operating model that succeeds when the path is unclear — which is almost always.

From collaboration to tradeoff

Almost every portfolio includes the word "collaborated." Which is good. Design is collaborative.

The frame that stands out is the one that names the tradeoff that collaboration produced. "We collaborated with engineering to balance development velocity against accessibility requirements." Or "Product wanted to ship by Q3, so we prioritized the core flow and deferred the personalization layer."

These examples show that the designer was not just present in the collaboration. They were shaping the decision about what to prioritize and what to accept as a cost. That is the difference between being a participant in the team's process and being a contributor to its judgment.

Why the Frame Matters Beyond the Interview

I want to be careful here. I am not writing about how to game an interview. The frame matters because it reflects something real.

The designers I have seen earn the most influence in product teams do not frame their work as delivery. They frame it as participation in the team's decision-making. That is not a storytelling trick. It is a description of how they actually operated.

When you are in the room where the tradeoff happens, you do not have to construct the frame later. It is already visible in the story. The research finding that changed the direction. The constraint that forced a creative compromise. The moment when the team realized something it had been assuming was wrong.

If the frame is missing from the story, it may be missing from the practice. And that is worth examining — not because of the interview, but because of the influence you are leaving on the table every day.

I have written before about how designers earn influence by reducing ambiguity and making reasoning visible. The frame shift I am describing here is the same idea from a different angle. The operating model matters. The way you describe it is a mirror of how you work.

The most useful question I have found for any designer at a career crossroads is not "What should I work on next?" It is "Can I describe my last project in terms of the decisions I helped the team make?"

If the answer is yes, the frame is already working. If it is no, the work is probably fine. The operating model might need the shift.