Subscribe to MiladyOnchain
<100 subscribers
Subscribe to MiladyOnchain
<100 subscribers
In-house design teams do two jobs at once: preserve craft and make product teams move faster. Tension appears when design must protect long-term quality while meeting short-term business targets. Fixes are operational and cultural: clearer intake, measurable work agreements, protected time for craft, and a small set of metrics that make design decisions visible. Evidence from companies that built DesignOps teams and robust design systems shows that these fixes scale design impact across products. Medium+1
Demand overflow and unclear prioritization
Design teams often become the bottleneck because every team views design as the last step before launch. Without a single demand intake and prioritization process, requests pile up and context is lost. Research and practitioner writing highlight strategic demand management as a top pain for in-house teams. Onward Search
Hand-off friction with engineering and product
A split between design artifacts and production code creates extra work and inconsistency. Teams that run separate design documentation sites or stray component libraries see higher maintenance costs over time. Atlassian and other organizations document costs of split docs and inconsistent systems. Medium+1
Stakeholder politics and scope creep
Design must balance product goals, revenue targets, and brand needs. Without simple rules for decision rights and a visible prioritization rubric, design becomes the place where competing demands meet, often at the expense of experience quality. Practitioner guides and leader reflections point to this as a common source of exhaustion. Medium
Burnout and invisible overhead
Creative work requires focus. Constant interruptions, reactive tasks, and emotional labor of mediating between teams lead to burnout. Leaders who fail to measure and protect creative capacity lose institutional knowledge and team cohesion. Medium
Use four linked levers: Intake, Contracts, Capacity, and Ops.
Intake - One source of truth for requests
Create a short demand intake form that forces a hypothesis, metric, and owner. If a request lacks those fields, it stays in backlog until filled. This reduces context switching and ensures design work maps to outcomes.
Contracts - One-page design agreements for each engagement
A light agreement clarifies scope, decision rights, deadlines, and success metrics. It prevents scope creep and makes tradeoffs explicit.
Capacity - Protect craft time with clear rules
Allocate a fixed percentage of team capacity to exploration and system work. Commit to review and defend that allocation in leadership meetings.
Ops - Small DesignOps investments to remove overhead
Centralize routine tasks like component maintenance, documentation hosting, and platform needs. A small DesignOps team or part-time coordinator often produces outsized returns by taking operational burden off designers.
Each lever is cheap to start and compoundingly valuable when combined. Airbnb and Atlassian show how focusing on Ops and systems reduces friction and lets designers work at scale. Medium+1
Request title
Requester and product owner
One-sentence problem statement
Hypothesis: if we change X, then Y will change by Z in T days
Primary metric (event name + definition)
Desired deliverable (copy/low-fi prototype/high-fi component)
Expected effort (S/M/L)
Decision rights (who approves scope / who approves visual sign-off)
Desired delivery date
Attachments / examples
Require this form to be complete before work is scheduled.
Project name
Purpose and success metric (one sentence)
Deliverables and fidelity (list)
Timeline and checkpoints (dates for discovery, prototype, handoff)
Decision roles: Product, Design, Engineering (who has final sign-off on scope, UX, and implementation)
Acceptance criteria (what counts as done)
Revise or cancel clause (how scope changes are handled)
Owner and stakeholders
Use this as a checklist during kickoff and attach it to the ticket.
Protect 10 percent capacity for exploration and system work.
No meetings on Tuesday mornings from 9-12 for focused work.
One weekly sync for urgent escalations only.
Quarterly rotation for at least one designer to lead a research spike.
Track compliance in team retro.
What they did
Airbnb built a DesignOps function to streamline design workflows, centralize tooling, and reduce repetitive coordination. DesignOps focused on hiring, tooling, and processes that let designers spend more time solving user problems rather than fighting operational overhead. Medium+1
Why it mattered
DesignOps reduced context switching and improved trust between design and engineering. By treating operational work as a first-class function, Airbnb scaled design contributions across many product teams while protecting craft time.
How to reproduce the effect in a small team
Hire or designate a DesignOps owner for 0.2 to 0.5 FTE.
Audit the top five recurring operational tasks designers perform and automate or delegate two of them within 30 days.
Measure designer time saved and track fewer escalations in sprint retro notes.
What they did
Atlassian invested in a design system to create one source of truth for components and patterns. They documented system, moved toward a single documentation site, and treated the system as a product that served other teams. Atlassian’s public reflections show how the system reduced inconsistencies and developer rework. UXPin+1
Why it mattered
A shared system saved engineering time, lowered design debt, and gave product teams faster, predictable building blocks. It allowed designers to focus on higher-level problems because common UI needs were already handled.
How to reproduce the effect in a mid-size org
Start with a component inventory and the top 10 reused patterns.
Build the smallest code-backed components and publish them as the first library.
Create a single documentation site and assign a steward to manage updates weekly.
Days 1-30 - Triage and intake
Audit incoming requests for the last 60 days and quantify average turnaround.
Launch demand intake form and require completion for new tickets.
Run a 90-minute design-team kickoff to set 10 percent protection rule.
Days 31-60 - Contracts and early Ops
Require one-page design contracts for all scoped work.
Identify one operational burden to remove (documentation hosting, handoff checklist) and fix it.
Run a pilot with two product teams using new intake + contract workflow.
Days 61-90 - Systemize and measure
Create a living design system inventory and publish a single docs site.
Measure time-to-delivery and designer satisfaction before and after changes.
Roll out a retro process that tracks creative protection compliance.
Pick 3 signals that matter and track them weekly:
Mean time from request accepted to design deliverable (days)
Percentage of requests with a completed intake form (target 100 percent)
Designer focus time per week (target is agreed protected hours)
Add qualitative signals like fewer escalations and improved stakeholder satisfaction.
Atlassian’s approach to quantifying UX challenges shows value of translating design issues into dollars and measurable outcomes; that makes design work visible to leadership. Atlassian
“We cannot slow down reviews with contracts.”
Response: one-page contract is a checklist, not legalese. It shortens later debates by making roles and success criteria visible upfront.
“We do not have bandwidth for DesignOps.”
Response: start with a 0.2 FTE owner or rotate role. The initial investment focuses on automating the single biggest interruption for designers.
“Creative work cannot be scheduled.”
Response: protect time for creative work, but keep it accountable. Ask designers to record learnings, prototypes, or outcomes so business sees the return.
In-house teams do their best work when product and design share a compact operating system: intake that forces clarity, contracts that set expectations, protected capacity for craft, and a small Ops function to reduce friction. Pick one lever to start this month. Which will you try first: intake, contracts, capacity protection, or ops?
Bookmark this for the future. See you next week!
Check out how we do it Chick.studio or DM me: LinkedIn • X
In-house design teams do two jobs at once: preserve craft and make product teams move faster. Tension appears when design must protect long-term quality while meeting short-term business targets. Fixes are operational and cultural: clearer intake, measurable work agreements, protected time for craft, and a small set of metrics that make design decisions visible. Evidence from companies that built DesignOps teams and robust design systems shows that these fixes scale design impact across products. Medium+1
Demand overflow and unclear prioritization
Design teams often become the bottleneck because every team views design as the last step before launch. Without a single demand intake and prioritization process, requests pile up and context is lost. Research and practitioner writing highlight strategic demand management as a top pain for in-house teams. Onward Search
Hand-off friction with engineering and product
A split between design artifacts and production code creates extra work and inconsistency. Teams that run separate design documentation sites or stray component libraries see higher maintenance costs over time. Atlassian and other organizations document costs of split docs and inconsistent systems. Medium+1
Stakeholder politics and scope creep
Design must balance product goals, revenue targets, and brand needs. Without simple rules for decision rights and a visible prioritization rubric, design becomes the place where competing demands meet, often at the expense of experience quality. Practitioner guides and leader reflections point to this as a common source of exhaustion. Medium
Burnout and invisible overhead
Creative work requires focus. Constant interruptions, reactive tasks, and emotional labor of mediating between teams lead to burnout. Leaders who fail to measure and protect creative capacity lose institutional knowledge and team cohesion. Medium
Use four linked levers: Intake, Contracts, Capacity, and Ops.
Intake - One source of truth for requests
Create a short demand intake form that forces a hypothesis, metric, and owner. If a request lacks those fields, it stays in backlog until filled. This reduces context switching and ensures design work maps to outcomes.
Contracts - One-page design agreements for each engagement
A light agreement clarifies scope, decision rights, deadlines, and success metrics. It prevents scope creep and makes tradeoffs explicit.
Capacity - Protect craft time with clear rules
Allocate a fixed percentage of team capacity to exploration and system work. Commit to review and defend that allocation in leadership meetings.
Ops - Small DesignOps investments to remove overhead
Centralize routine tasks like component maintenance, documentation hosting, and platform needs. A small DesignOps team or part-time coordinator often produces outsized returns by taking operational burden off designers.
Each lever is cheap to start and compoundingly valuable when combined. Airbnb and Atlassian show how focusing on Ops and systems reduces friction and lets designers work at scale. Medium+1
Request title
Requester and product owner
One-sentence problem statement
Hypothesis: if we change X, then Y will change by Z in T days
Primary metric (event name + definition)
Desired deliverable (copy/low-fi prototype/high-fi component)
Expected effort (S/M/L)
Decision rights (who approves scope / who approves visual sign-off)
Desired delivery date
Attachments / examples
Require this form to be complete before work is scheduled.
Project name
Purpose and success metric (one sentence)
Deliverables and fidelity (list)
Timeline and checkpoints (dates for discovery, prototype, handoff)
Decision roles: Product, Design, Engineering (who has final sign-off on scope, UX, and implementation)
Acceptance criteria (what counts as done)
Revise or cancel clause (how scope changes are handled)
Owner and stakeholders
Use this as a checklist during kickoff and attach it to the ticket.
Protect 10 percent capacity for exploration and system work.
No meetings on Tuesday mornings from 9-12 for focused work.
One weekly sync for urgent escalations only.
Quarterly rotation for at least one designer to lead a research spike.
Track compliance in team retro.
What they did
Airbnb built a DesignOps function to streamline design workflows, centralize tooling, and reduce repetitive coordination. DesignOps focused on hiring, tooling, and processes that let designers spend more time solving user problems rather than fighting operational overhead. Medium+1
Why it mattered
DesignOps reduced context switching and improved trust between design and engineering. By treating operational work as a first-class function, Airbnb scaled design contributions across many product teams while protecting craft time.
How to reproduce the effect in a small team
Hire or designate a DesignOps owner for 0.2 to 0.5 FTE.
Audit the top five recurring operational tasks designers perform and automate or delegate two of them within 30 days.
Measure designer time saved and track fewer escalations in sprint retro notes.
What they did
Atlassian invested in a design system to create one source of truth for components and patterns. They documented system, moved toward a single documentation site, and treated the system as a product that served other teams. Atlassian’s public reflections show how the system reduced inconsistencies and developer rework. UXPin+1
Why it mattered
A shared system saved engineering time, lowered design debt, and gave product teams faster, predictable building blocks. It allowed designers to focus on higher-level problems because common UI needs were already handled.
How to reproduce the effect in a mid-size org
Start with a component inventory and the top 10 reused patterns.
Build the smallest code-backed components and publish them as the first library.
Create a single documentation site and assign a steward to manage updates weekly.
Days 1-30 - Triage and intake
Audit incoming requests for the last 60 days and quantify average turnaround.
Launch demand intake form and require completion for new tickets.
Run a 90-minute design-team kickoff to set 10 percent protection rule.
Days 31-60 - Contracts and early Ops
Require one-page design contracts for all scoped work.
Identify one operational burden to remove (documentation hosting, handoff checklist) and fix it.
Run a pilot with two product teams using new intake + contract workflow.
Days 61-90 - Systemize and measure
Create a living design system inventory and publish a single docs site.
Measure time-to-delivery and designer satisfaction before and after changes.
Roll out a retro process that tracks creative protection compliance.
Pick 3 signals that matter and track them weekly:
Mean time from request accepted to design deliverable (days)
Percentage of requests with a completed intake form (target 100 percent)
Designer focus time per week (target is agreed protected hours)
Add qualitative signals like fewer escalations and improved stakeholder satisfaction.
Atlassian’s approach to quantifying UX challenges shows value of translating design issues into dollars and measurable outcomes; that makes design work visible to leadership. Atlassian
“We cannot slow down reviews with contracts.”
Response: one-page contract is a checklist, not legalese. It shortens later debates by making roles and success criteria visible upfront.
“We do not have bandwidth for DesignOps.”
Response: start with a 0.2 FTE owner or rotate role. The initial investment focuses on automating the single biggest interruption for designers.
“Creative work cannot be scheduled.”
Response: protect time for creative work, but keep it accountable. Ask designers to record learnings, prototypes, or outcomes so business sees the return.
In-house teams do their best work when product and design share a compact operating system: intake that forces clarity, contracts that set expectations, protected capacity for craft, and a small Ops function to reduce friction. Pick one lever to start this month. Which will you try first: intake, contracts, capacity protection, or ops?
Bookmark this for the future. See you next week!
Check out how we do it Chick.studio or DM me: LinkedIn • X
Share Dialog
Share Dialog
No comments yet