Planning Strategy, Structure, Systems
Strategy keeps the team focused on what matters most as priorities shift. Structure provides a shared roadmap that guides how work is organized and executed. Systems create the repeatable processes that enable collaboration, consistency, and scale.
Strategy
Stay aligned with shifting business priorities and market conditions. Strategy gives direction. It helps you decide what matters now, what matters later, and what does not matter at all.
Framework diagrams are powerful tools for making complex information clear. They can capture multidimensional objects such as people, roles, cross‑department dependencies, flow of work, platforms, systems and environments.
Framework 1 - High-level Operations
When you discover something you can go deep on—something that feels meaningful—it changes how you show up. Work becomes easier, more engaging, and sometimes even enjoyable.
Framework 2 - Strategic themes, pillars, focus areas
When you discover something you can go deep on—something that feels meaningful—it changes how you show up. Work becomes easier, more engaging, and sometimes even enjoyable.
Framework 3 - Anatomy of a focus area card
When you discover something you can go deep on—something that feels meaningful—it changes how you show up. Work becomes easier, more engaging, and sometimes even enjoyable.
Framework 4 - Focus area cards into goals and objectives
When you discover something you can go deep on—something that feels meaningful—it changes how you show up. Work becomes easier, more engaging, and sometimes even enjoyable.
Framework 5 - Aligning goals around the other areas of business
When you discover something you can go deep on—something that feels meaningful—it changes how you show up. Work becomes easier, more engaging, and sometimes even enjoyable.
Implementation, impact, results
Whether it’s a rough whiteboard sketch or a polished, detailed graphic, diagrams help people understand how work connects and how teams operate.
Strong diagramming is a core skill in my toolkit because it simplifies complexity and builds shared understanding.
Structure
Build a clear structure and roadmap that shows where you are going and why. Structure creates shared understanding. It helps teams see the work ahead, sequence decisions, and move in the same direction.
Structuring People
I’ve seen structure help teams thrive, and others bog them down. Striking a balance between autonomy and structure so creative people can do their best work is at the core of design leadership.
Organizational Structure
A strong structure empowers people to lead, collaborate, and deliver meaningful outcomes. Structure should clarify how the design team operates while ensuring it is fully integrated with the rest of the organization.
Define Clear Roles and Reporting Lines
Make the design team's place in the organization explicit. Clearly outline roles, responsibilities, and reporting lines so people understand who does what, how decisions are made, and how work flows across teams. Clarity reduces friction and speeds up execution.
Empower Through Structure
Design leaders need room to make decisions, set direction, and influence outcomes. Build a structure that supports autonomy while also enabling tight partnerships with product, engineering, marketing, and other critical teams.
Collaboration Structures
Codify how remote and hybrid teams work together, how decisions move across functions, and where shared accountability lives. When collaboration is structured and transparent, teams move faster, reduce rework, and create better outcomes for customers and the business.
Structuring Meetings
I’ve seen structure help teams thrive, and others bog them down. Striking a balance between autonomy and structure so creative people can do their best work is at the core of design leadership.
Stand‑Ups
I’ve run stand‑ups both synchronously and asynchronously. My preferred model is a 2–3 times per week synchronous design stand‑up.
Serve three purposes:
They help designers prioritize and stay focused.
They give me a quick way to spot misalignment and redirect early.
They show the team who is blocked and where collaboration is needed.
Open Workshops
one open workshop per week, also immediately after a stand‑up.
This time serves multiple purposes:
Team brainstorming
Helping someone unblock a problem
Cross‑pollination of ideas
Running structured workshops when needed
The consistency builds trust — designers and researchers know they will always have a space to think together as a team.
Design Critiques
A weekly critique at a consistent time works well. I schedule it immediately after a stand‑up to create a natural transition into deeper work.
This gives designers regular space to review work early, gather feedback, and course‑correct before anything gets too far along.
Focus Time
I encourage designers and researchers to block dedicated focus time on their calendars and bundle their meetings.
This helps them:
Protect deep work
Strategize without interruption
Reach flow state
Produce higher‑quality outcomes
It also supports retention. When people feel they have space to do meaningful work instead of being pulled in every direction, they stay longer.
Structuring Competing Priorities
Create contextual roadmaps that give teams a shared understanding of where they are going and why. A well‑structured roadmap aligns priorities, clarifies expectations, and shows the sequence of work required to reach your goals. It helps teams stay focused, communicate progress, and make informed decisions as priorities shift.
A strong roadmap should show:
What needs to be done
Why it matters
When work is expected to happen
How initiatives connect to business objectives
Where teams depend on each other
When teams have a shared view of the path ahead, they move with confidence and avoid unnecessary rework.
A pain point journey map should show:
What needs to be done
Why it matters
When work is expected to happen
How initiatives connect to business objectives
Where teams depend on each other
When teams have a shared view of the path ahead, they move with confidence and avoid unnecessary rework.
A prioritization matrix should show:
What needs to be done
Why it matters
When work is expected to happen
How initiatives connect to business objectives
Where teams depend on each other
When teams have a shared view of the path ahead, they move with confidence and avoid unnecessary rework.
Systems
Create systems that support collaboration, diverse disciplines, and organizational scale. Systems make work repeatable, predictable, and easier for people to succeed in.
Build efficient processes and workflows supported by the right project management and communication tools. Define how work moves through the team, how decisions are made, and how information is shared. When systems are predictable and well‑maintained, teams execute faster and with fewer errors, and give teams more time to focus on meaningful work.
Design Operating Model
The connective tissue of the entire team.
A medium‑sized team needs:
A design ops function (formal or part‑time)
Process owners
Tool administrators
A roadmap for operational improvement
Metrics to measure system health
DesignOps maintains everything above.
Design System, UI Patterns & Components Consistency, speed, quality, accessibility.
You need:
A component library (Figma components + coded equivalents)
Usage guidelines
Accessibility requirements baked into components
Pattern documentation
Versioning rules
A formal governance model
This is the system that makes the rest of the team faster.
Design at scale system
After a strong, component‑based design system is essential for scaling. As large sections of a product or website mature and shift into a management and maintenance phase, the focus moves toward identifying common patterns and documenting ecosystems of templates, page types, and reusable structures.
This approach empowers teams to design ahead with predefined solutions. It reduces manual work, increases predictability, and accelerates delivery across functions.
Knowledge Management System
A single source of truth.
Must include
A unified repository for design artifacts
Version control for assets
A shared decision log
Team guidelines and playbooks
Templates for repeatable work
Recorded research, diagrams, and process documentation
This reduces “lost knowledge” and onboarding time.
Modular Content at scale
Ensure output quality and alignment.
Must include:
Modular Content Systems
Accessibility reviews
Copy/content reviews
Engineering feasibility checks
Design QA before release
Post‑launch evaluations
Stable quality systems reduce rework and build trust with partners.
Governance & Decision‑Making Systems
Keep decisions transparent and scalable.
Includes:
Decision logs
Approvals workflows
Ownership maps (RACI or similar)
A clear process for updating systems, patterns, and workflows
Good governance prevents design systems, processes, and workflows from drifting into chaos.
Workflow & Delivery Systems
Predictable, transparent work execution.
You need systems that define:
How work requests come in
How work is prioritized
How designers hand off work to engineering
How design, product, and engineering sync
Where documentation lives
What “definition of done” means for design
Dynamic content delivery systems
Internationalization (i18n) System
Localization workflow
Translation management
Layout rules for global languages
A/B testing segmentation rules for international traffic
Guidelines for market‑specific customization
A medium‑sized team that serves global users can’t skip this.