One of the biggest shifts in how I work: I stopped treating delivery as something that happens after discovery. Because that's usually where good ideas fall apart.
A solution can look great on paper — clear problem, strong logic, aligned stakeholders.
But if you haven't pressure-tested:
- how it will actually be built
- how it integrates into existing systems
- how it can be sequenced and shipped incrementally
…it's still fragile.
Now, I pull delivery thinking into discovery early.
Not to slow things down — but to avoid designing things that can't survive real-world constraints.
In practice, this means I'm constantly asking:
- “Could we actually ship this?”
- “What breaks when this hits production?”
- “What's the smallest version of this that creates value?”
That shift alone has probably saved more time than any process improvement I've made.