How to Regain Design Influence When the Problem's Set
For In-house product designers on pre-defined projects · Based on Aliena Cai AI-Augmented Design Method
// TL;DR
If you're an in-house product designer handed a finished PRD and told to deliver screens, the Aliena Cai AI-Augmented Design Method helps you reclaim influence. This is Severe Shrinkage of the First Diamond — the problem and solution pre-defined before you joined. The counter-move is the Three Stakeholder Emails, drafted with AI from the business stakeholder's perspective, to reopen discovery, run a kick-off alignment meeting, and propose primary user interviews. When engineers push back on complex interactions, prototype in Figma Make instead of debating feasibility — shifting the conversation to authority.
What do I do when the problem and solution were decided without me?
Recognize it for what it is: Severe Shrinkage of the First Diamond. When business stakeholders pre-define both the problem and the solution before you're involved, you're left with a visualization role and no ability to influence direction or impact. The first step is to flag this explicitly — audit whether the First Diamond was genuinely worked, or whether it was skipped.
Being handed a finished PRD and told to deliver designs immediately is the classic symptom. You don't have to accept the shrunk role.
How do the Three Stakeholder Emails reopen the problem space?
The Three Stakeholder Emails are the specific counter-tactic, and AI makes them more persuasive by drafting each from the business stakeholder's perspective:
1. Email 1 — to the project owner, requesting inclusion in the discovery meeting before the PM finalizes the PRD.
2. Email 2 — a kick-off alignment meeting invite to all relevant stakeholders (PM, content designer, data analyst, engineers, legal, UX researchers) so everyone shares ideas before the problem is locked.
3. Email 3 — to the UX research team and PM, proposing a short primary user interview plan to get approval before design begins.
Ask AI to write each from the angle that most convinces that audience. Even a small research window can change direction and expand your influence before a single screen is designed.
Why does primary research still matter here?
Because AI-generated research is not a substitute for first-hand user learning. If the business pre-defined the problem based on assumptions, primary research is exactly what tests those assumptions. Use AI in support roles — drafting recruiting emails, generating stronger interview questions, preparing faster, and using note-taking tools like Granola as backup. But you must personally review, polish, and analyze the notes. Nuance and meaning are easy to miss, and the judgment is yours.
How do I stop engineers from vetoing complex interactions?
Never present a static annotation for a complex interaction — like sortable, draggable table columns — because it invites a 'that's too hard' response. Instead, select the frame in Figma, right-click → Send to Figma Make, describe the interaction in plain language, and generate a functional prototype in minutes.
Demoing a working interaction shifts the conversation from 'is it possible?' to 'does this feel right?' — a position of far greater design authority. You've moved the debate from feasibility, where engineers hold the power, to experience quality, where you do.
How do I protect my work and my case studies?
Document every major iteration. Keep the latest version at the top of your Figma file, allocate one page per iteration, and annotate what changed, why, and who requested it. Use ChatGPT to convert rough notes into clean point-form annotations, and paste AI meeting summaries as a baseline.
Undocumented iterations force rework when stakeholders ask 'have you tried X?' and make defensible case studies impossible. Documentation is not optional — it's what protects your influence over time.
What's my next step?
On your next pre-defined project, audit the First Diamond honestly. If it's been shrunk, draft the Three Stakeholder Emails with AI today — request discovery access, propose a kick-off alignment meeting, and pitch a short primary interview plan. When a complex interaction comes up, prototype it in Figma Make before the engineering conversation. Document every iteration as you go.
// FREQUENTLY ASKED QUESTIONS
What if my manager resists the Three Stakeholder Emails?
Frame each email from the business stakeholder's perspective — AI helps you write persuasively to that audience. Emphasize that reopening discovery reduces the risk of building the wrong thing, which is the most expensive failure mode. You're not slowing delivery; you're protecting the business from months spent solving a problem that may not exist. Even a small research window helps.
Can I use AI note-taking tools during user interviews?
Yes, as backup — tools like Granola are acceptable — but you must personally review, polish, and analyze the notes afterward. Nuance and meaning are easy to miss, and the synthesis is where your judgment lives. AI captures the raw material; you own the interpretation. Never let AI notes stand in for your own analysis of what users actually meant.
When should I bring a Figma Make prototype back into Figma?
Once the interaction is approved. Designing entirely in AI tools without returning to a proper Figma file — with design system adherence and clear specs for engineering — is a pitfall. After you demo the Figma Make prototype and it moves forward, bring it into your Figma file, annotate how it works, and make clear the demo is a reference, not the final spec.