Bindu Prahlad
DESIGN PRACTICE
DELIVERY SYSTEM
THE SAME
TEN DAYS.
EVERY
PROJECT.
12 PEOPLE.
6 COUNTRIES.
1 CADENCE.
DAY 01
PLAN
DAY 02–03
DESIGN
DAY 04
REVIEW
FEASIBILITY
THE INTERVENTION
DAY 06–07
REVISE
DAY 08
CLIENT
DAY 09–10
SUBMIT
01 → 10
DAY 05
SECTOR
Across sectors
MARKET
UAE & KSA
MY ROLE
Design Manager
STAKEHOLDERS
Executive Leadership
TOOLS
Figma · Miro · Jira
THE PROBLEM
DESIGN WENT QUIET
FOR WEEKS,
THEN ARRIVED
ALL AT ONCE.
Clients waited for a reveal. Feedback arrived too late to be cheap. And engineering saw the work only after client sign-off.
BEFORE
DESIGN
SILENCE
CLIENT REVEAL
FEEDBACK
ENGINEERING
REWORK
SO I STOPPED DESIGNING
THE DELIVERABLE AND
DESIGNED THE TWO WEEKS.
WHAT I ACTUALLY CHANGED
01
THE CADENCE
I changed the work from an open-ended design phase into a fixed ten-day rhythm.
02
THE DECISION POINT
I moved engineering feasibility into Day 05, while design could still change.
03
THE CLIENT EXPERIENCE
I replaced the reveal model with visible progress throughout the sprint.
04
THE SYSTEM
I documented the cadence so distributed teams could run it consistently without depending on me.
STEP 00 — BEFORE DAY ONE
WHAT DID THE CLIENT
ACTUALLY SEND?
MATURE BRD?
YES
START THE SPRINT.
DAY 01
NO
BRIEF VALIDATION
BRD + BACKLOG
START THE SPRINT.
THE BRIEF-ONLY BRANCH IS ITS OWN CASE STUDY →
THE OPERATING MODEL
Inside the ten days.
Two rituals hold it together: a standing backlog, and a planning session that opens every sprint.
01
Sprint planning
From a standing backlog, not the brief.
02–03
Design
Against the system. Copy written, not faked.
04
Internal review
Critiqued before anyone outside the team sees it.
05
Tech feasibility
Reviewed while it can still change. The step I added.
06–07
Revise
Two days on both reviews at once.
08
Client review
Progress, not a reveal.
09–10
Submission
Day ten. Every time.
“If I could keep only one step of the ten, I would keep this one.”
DAY 05 — FEASIBILITY — ENGINEERING ENTERS HERE.
ENGINEERS
REVIEW
THE WORK
BEFORE
THE CLIENT
DOES.
BEFORE
DESIGN
→
CLIENT SIGN-OFF
→
ENGINEERING
→
REWORK
AFTER
DESIGN
→
ENGINEERING FEASIBILITY
→
REVISION
→
CLIENT
I moved the decision earlier,
while the design could still change.
THE RESISTANCE
Engineering already ran sprints — planning, retrospectives, a proper cadence. Design was the exception: work arrived late, unplanned, and we were expected to absorb it.
THE OBJECTION WAS NOT
TO THE SPRINT.
IT WAS TO DESIGN
HAVING ONE.
WHO PUSHED BACK
Leadership, and the engineering team in particular.
WHAT IT WAS ACTUALLY ABOUT
A fixed cadence meant work could no longer arrive at the end for design to absorb. It had to be planned.
Nothing was settled by argument. It settled once the cadence was running, and the same people came on board.
WHAT CHANGED
10 DAYS
Predictable delivery.
PROGRESS,
NOT REVEAL
A different client experience.
FEASIBILITY
BEFORE SIGN-OFF
Lower rework risk.
BACKLOG
BEFORE MONDAY
A more predictable start.
THE PRACTICE
12 PEOPLE.
6 COUNTRIES.
1 CADENCE.
The sprint is written down, so a team in another time zone opens a project the same way I would.
ONE CADENCE, SIX PLACES
01
02
03
04
05
06
01
PLAN
02
DESIGN
03
DESIGN
04
REVIEW
05
FEASIBILITY
06
REVISE
07
REVISE
08
CLIENT
09
SUBMIT
10
SUBMIT
THE SAME TEN DAYS — AND THE SAME DAY 05 — WHEREVER THE TEAM SITS
A WAY OF WORKING
THE TEAM KEEPS
WHEN I AM NOT
IN THE ROOM.
THE CONNECTED PRACTICE
Two branches of the same model.
THE BRIEF-ONLY BRANCH
Turning a one-line brief into a full product plan
DISCOVERY SYSTEM →
MAKING A REVIEW A DECISION
How visual direction stopped being a matter of taste
RESIDENT APP →
THE LESSON
01
Delivery that is predictable
before it is impressive.
02
Design judgment placed
where it changes the cost,
not after it.
03
A way of working the team
keeps when I am not
in the room.
“The cadence was never for us.
It was a promise to everyone
who had to wait for design.”
Stay Curious. Keep Moving.
01
PLAN
02
DESIGN
03
DESIGN
04
REVIEW
05
FEASIBILITY
06
REVISE
07
REVISE
08
CLIENT
09
SUBMIT
10
SUBMIT
DESIGN PRACTICE
THE SAME
TEN DAYS.
EVERY
PROJECT.
12 PEOPLE.
6 COUNTRIES.
1 CADENCE.
01 → 10
DAY 05
SECTOR
Across sectors
MARKET
UAE & KSA
MY ROLE
Design Manager
STAKEHOLDERS
Executive Leadership
TOOLS
Figma · Miro · Jira
THE PROBLEM
DESIGN WENT QUIET
FOR WEEKS,
THEN ARRIVED
ALL AT ONCE.
Clients waited for a reveal. Feedback arrived too late to be cheap. And engineering saw the work only after client sign-off.
BEFORE
DESIGN
SILENCE
CLIENT REVEAL
FEEDBACK
ENGINEERING
REWORK
SO I STOPPED DESIGNING
THE DELIVERABLE AND
DESIGNED THE TWO WEEKS.
WHAT I ACTUALLY CHANGED
01
THE CADENCE
I changed the work from an open-ended design phase into a fixed ten-day rhythm.
02
THE DECISION POINT
I moved engineering feasibility into Day 05, while design could still change.
03
THE CLIENT EXPERIENCE
I replaced the reveal model with visible progress throughout the sprint.
04
THE SYSTEM
I documented the cadence so distributed teams could run it consistently without depending on me.
STEP 00 — BEFORE DAY ONE
WHAT DID THE CLIENT
ACTUALLY SEND?
MATURE BRD?
YES
START THE SPRINT.
NO
BRIEF VALIDATION
BRD + BACKLOG
START THE SPRINT.
THE BRIEF-ONLY BRANCH IS ITS OWN CASE STUDY →
THE OPERATING MODEL
INSIDE THE
TEN DAYS.
Two rituals hold it together: a standing backlog, and a planning session that opens every sprint.
01
Sprint planning
From a standing backlog, not the brief.
02–03
Design
Against the system. Copy written, not faked.
04
Internal review
Critiqued before anyone outside the team sees it.
05
Tech feasibility
Reviewed while it can still change. The step I added.
06–07
Revise
Two days on both reviews at once.
08
Client review
Progress, not a reveal.
09–10
Submission
Day ten. Every time.
DAY 05 — FEASIBILITY — ENGINEERING ENTERS HERE.
ENGINEERS
REVIEW
THE WORK
BEFORE
THE CLIENT
DOES.
BEFORE
DESIGN
↓
CLIENT SIGN-OFF
↓
ENGINEERING
↓
REWORK
AFTER
DESIGN
↓
ENGINEERING FEASIBILITY
↓
REVISION
↓
CLIENT
I moved the decision earlier,
while the design could still change.
“If I could keep only one step of the ten, I would keep this one.”
THE RESISTANCE
Engineering already ran sprints — planning, retrospectives, a proper cadence. Design was the exception: work arrived late, unplanned, and we were expected to absorb it.
THE OBJECTION WAS NOT
TO THE SPRINT.
IT WAS TO DESIGN
HAVING ONE.
WHO PUSHED BACK
Leadership, and the engineering team in particular.
WHAT IT WAS ACTUALLY ABOUT
A fixed cadence meant work could no longer arrive at the end for design to absorb. It had to be planned.
Nothing was settled by argument. It settled once the cadence was running, and the same people came on board.
WHAT CHANGED
10 DAYS
Predictable delivery.
PROGRESS,
NOT REVEAL
A different client experience.
FEASIBILITY
BEFORE SIGN-OFF
Lower rework risk.
BACKLOG
BEFORE MONDAY
A more predictable start.
THE PRACTICE
12 PEOPLE.
6 COUNTRIES.
1 CADENCE.
The sprint is written down, so a team in another time zone opens a project the same way I would.
ONE CADENCE, SIX PLACES
01
02
03
04
05
06
07
08
09
10
01
02
03
04
05
06
THE SAME DAY 05, WHEREVER THE TEAM SITS
A WAY OF WORKING
THE TEAM KEEPS
WHEN I AM NOT
IN THE ROOM.
THE SYSTEM SCALE
TWO BRANCHES OF
THE SAME MODEL.
THE BRIEF-ONLY BRANCH
Turning a one-line brief into a full product plan
DISCOVERY SYSTEM →
MAKING A REVIEW A DECISION
How visual direction stopped being a matter of taste
RESIDENT APP →
THE LESSON
01
DELIVERY THAT IS PREDICTABLE
BEFORE IT IS IMPRESSIVE.
02
DESIGN JUDGMENT PLACED
WHERE IT CHANGES THE COST,
NOT AFTER IT.
03
A WAY OF WORKING
THE TEAM KEEPS
WHEN I AM NOT IN THE ROOM.
“The cadence was never
for us. It was a promise
to everyone who had
to wait for design.”
Stay Curious. Keep Moving.
Bindu Prahlad