DESIGN DELIVERY

Planning

OVERVIEW

Best-Laid Delivery Plans

Long before I led a design team, I worked as an IT management consultant. Year after year, I heard the same complaint from Fortune 500 CIOs: project estimates were rarely accurate, and missed deadlines drove costly overruns. Once I owned delivery timelines myself, I understood why. Discovery answered some questions, but design was where complexity multiplied—through evolving workflows, emerging edge cases, and the iteration required to make products usable. I needed a better way to scope the work, plan resources, and offer a more credible timeline before every unknown had been resolved.

OVERVIEW

Best-Laid Delivery Plans

OVERVIEW

Best-Laid Delivery Plans

MY APPROACH

Don't Reinvent the Wheel

Rather than inventing a planning model from scratch, I borrowed from agile delivery. By studying sprint-planning practices and working with project managers, I adapted concepts like work breakdown, dependency mapping, and sequencing into a design-focused framework for estimating effort, improving throughput, and planning more predictable delivery.

MY APPROACH

Don't Reinvent the Wheel

ACTIVITY BREAKDOWN

BEST PRACTICE RESEARCH

60%

IDEATION SESSIONS

40%

EXPLORE

Ideation Sessions with Project Managers

I met with project managers to brainstorm how to apply sprint planning practices to design work, defining units of work, sequencing delivery, and allocating tasks across specialties to improve throughput and reduce ambiguity.

BUILD

Researched Sprint Planning Practices

I studied Agile sprint planning methods through targeted research and hands-on experience, focusing on story pointing, dependency mapping, and planning workflows. This gave me the foundation to introduce more structured, predictable planning across the team.

EXPLORE

Ideation Sessions with Project Managers

BUILD

Researched Sprint Planning Practices

EXPLORE

Ideation Sessions with Project Managers

BUILD

Researched Sprint Planning Practices

EXPLORE

Ideation Sessions with Project Managers

BUILD

Researched Sprint Planning Practices

Problems to Solve

This work surfaced four issues the new delivery planning process had to solve

This work surfaced four issues the new delivery planning
process had to solve

01 / PROJECT SCOPING

Too Big to Succeed

Design work was not broken into units small and clear enough to estimate, assign, and complete within a two-week sprint.

01 / PROJECT SCOPING

Too Big to Succeed

Design work was not broken into units small and clear enough to estimate, assign, and complete within a two-week sprint.

O2 / TASK SEQUENCING

Going the Wrong Way

Dependencies between features, workflows, and reusable components made it difficult to sequence work efficiently and avoid bottlenecks.

O2 / TASK SEQUENCING

Going the Wrong Way

Dependencies between features, workflows, and reusable components made it difficult to sequence work efficiently and avoid bottlenecks.

03 / TEAM THROUGHPUT

One Lane at a Time

Without a better way to divide work across UX, visual, and motion design, the team struggled to work in parallel and maintain momentum.

03 / TEAM THROUGHPUT

One Lane at a Time

Without a better way to divide work across UX, visual, and motion design, the team struggled to work in parallel and maintain momentum.

04 / DESIGN HANDOFF

Growth Without Investment

The lack of a consistent delivery cadence made it difficult to predict when design work would be ready for development.

04 / DESIGN HANDOFF

Growth Without Investment

The lack of a consistent delivery cadence made it difficult to predict when design work would be ready for development.

The Solution

Designing digital products well requires more than creativity—it requires structure, sequencing, and a delivery rhythm the broader team can trust. To make design work easier to scope and plan, I created a framework for breaking products into manageable parts, sizing effort by complexity, and organizing work into two-week sprints. This gave the team a more predictable path from early concepts to developer-ready design.

KEY DELIVERABLES

PLANNING FRAMEWORK

•

ESTIMATION GUIDELINES

The Solution

KEY DELIVERABLES

PLANNING FRAMEWORK

ESTIMATION GUIDELINES

PLANNING FRAMEWORK

From Scope to Sprint

I created a 5-step sprint planning framework that turns messy product scope into a predictable design delivery schedule — breaking work into manageable parts, sizing complexity, sequencing priorities, and keeping strategy and execution moving in parallel.

Define

Size

Plan

Sequence

Stagger

Define the Product Building Blocks

Break digital products into their essential building blocks: workflows, navigation, key pages, content blocks, and reusable components. This turns a vague product scope into a clear set of parts, making it easier to understand what needs to be designed, estimated, sequenced, and delivered.

OUTPUT

A clear inventory of design work

Size the Design Effort

Estimate design work by complexity, not screen count. A single page can require complex filtering, new patterns, or unresolved requirements. T-shirt sizing helps teams account for feature complexity, exploration, stakeholder review, and unknowns that may surface during early concept work.

OUTPUT

A rough estimate for each unit of work

Plan Each Sprint

T-shirt sizing helps teams determine how many work units can realistically fit into each two-week sprint. From there, they can fill each sprint slot with the right mix of design tasks, creating a predictable release rhythm for product and engineering.

OUTPUT

A clear inventory of design work

Sequence the Work

Start with simpler pages to establish the product’s look, feel, and reusable patterns. Then move into core features where the hardest decisions are about how the experience works. Save homepages and dashboards for last, once the components they summarize have already been designed.

OUTPUT

A smarter sequence of interdependent design sprints

Stagger the Design Tracks

Run experience design and visual design in overlapping tracks. Experience designers shape workflows, wireframes, and feature structure while visual designers refine sprint work into polished prototypes. This keeps the baton moving across sprints and prevents teams from waiting on handoff.

OUTPUT

Continuous momentum throughout the design sprint

Define the Product Building Blocks

OUTPUT

A clear inventory of design work

Size the Design Effort

OUTPUT

A rough estimate for each unit of work

Plan Each Sprint

OUTPUT

A clear inventory of design work

Sequence the Work

OUTPUT

A smarter sequence of interdependent design sprints

Stagger the Design Tracks

OUTPUT

Continuous momentum throughout the design sprint

Lessons Learned

This work taught me that design delivery becomes more predictable when teams stop treating design as an abstract creative phase and start breaking it down into visible, estimable units of work. Screen counts alone were not enough to understand effort; the real complexity lived in workflows, dependencies, unresolved requirements, interaction patterns, and the amount of iteration needed to make the experience usable. By borrowing from agile planning and adapting those methods for design, I learned how to create a shared language for complexity that helped product, design, engineering, and project management plan with more confidence. It also reinforced that speed is not just about working faster—it is about sequencing smarter. Starting with foundational pages, delaying dashboards and summary views until the underlying components were defined, and staggering experience and visual design tracks helped the team maintain momentum without rushing decisions prematurely. The framework gave design a clearer delivery rhythm, reduced ambiguity for stakeholders, and made timelines feel less like guesses and more like informed plans. Most importantly, it showed that strong design leadership requires both creative judgment and operational discipline.