One of the most important steps in building your company’s design culture is establishing a design cadence. My teams have found success in the iterative cycles of Discover, Define, Test, and Deploy.
To meet the customers needs, a design approach should make space for discovery, and allow for cyclical iteration between testing, definition, measurement and back again. Unfortunately not all design sprints allow for early user testing or deep data analytics. Sometimes you just need tighter cycles where you can gather data once the feature is in market.
It’s absolutely critical though that the team have a shared understanding of what the intent, actions and expected deliverables are for each phase. For example, coming out of discovery, the team should be aligned on a set of prioritized user needs, use cases and edge cases, before moving to design definition.
No two teams are alike so consider your market and unique business needs, improvise, experiment and don’t be afraid to fail!