It's more than drawing on a whiteboard and saying the word "disruptive".
We concretely identify important aspects of our approach early and often. The objective is to dispel confusion around what we’re trying to solve, validate the problem, and to determine whether it should be included within the current scope. To take it a step further, establishing KPI’s (key performance indicators) enable measurement of success. When later iterating on a design, I can better distinguish what works from what doesn’t, and therefore make coherent recommendations for or against future tactics.
Design strategy and approach will always be defined by the needs of a particular project, however you should always at baseline ensure that everyone is moving as a cohesive team (including external stakeholders). Conflict is part of the process, but has to be addressed early and often. To facilitate, I have a toolbox of exercises take teams cohesively from brainstorms to initial iterations of a product. Keeping the team aligned ensures a project is executed thoughtfully and smoothly.
Project planning & Scope
Thinking about what it will take to execute on a tactic. By now I would have asked about any constraints that need to be considered such as timeline and budget. Taking those considerations into account I may lay out several approaches but recommend the one that best suits the imperative.