how do i find a partner for design thinking and ideation sprints?
a good design thinking or ideation sprint focuses a team on a clearly defined question. a suitable consulting approach combines problem understanding, idea generation, and early validation. when making your selection, you should consider whether the format aligns with your level of uncertainty and what decision will ultimately be made.
scope of services and delimitation
in design thinking, the scope of work should clearly specify which results the design partner is responsible for. technical documentation, approvals, and specialized engineering or technical planning services must be explicitly assigned to the relevant technical partners wherever they are required.
a testable hypothesis instead of a full idea board
having many ideas doesn’t necessarily mean progress if it remains unclear which ones are needed. a well-designed sprint brings the most important assumption to light. this could be the ease of understanding a new service or the usability of a product. a suitable prototype must answer precisely this question. a clickthrough model and a physical mockup are therefore not interchangeable.
four criteria for choosing a partner
- relevant references: evaluate the team’s actual contribution to the project.
- methods appropriate to the question: workshops, models, or tests are means to an end.
- practicality: results must be transferable to the next phase of development.
- clear boundaries: design, engineering, production, and other specialized roles require clearly defined responsibilities.
project process and decisions
start by defining the objective, boundary conditions, and decision criteria. develop alternative solution approaches and evaluate critical assumptions early on. document approvals and open issues before moving on to the next level of detail. you can find more information on this in the design consulting by f/p design.
example of a typical decision
if there are several possible solutions, the team should not simply choose the one that looks the most appealing. compare utility, technical feasibility, brand impact, cost implications, and potential risks. this leads to a well-reasoned decision rather than a matter of personal preference.
common mistakes in selection and contracting
unclear deliverables and methods that lack a specific decision question can be problematic. you should also avoid deriving technical or regulatory certainty from a conceptual prototype. each test should specify exactly what conclusions it can actually draw.
compare costs and schedules effectively
costs arise from research, variations, prototypes, testing, and iterative refinement. have each phase and result reported separately. this will help you determine whether quotes cover the same scope of work.
the briefing for an initial meeting
describe the objective, users, current status of development, and known constraints. provide any available data, models, or technical documentation. list the relevant subject matter experts involved and highlight the most important pending decisions.
frequently asked questions about design thinking and ideation sprints
when should a design partner get started?
early enough that fundamental decisions can still be influenced. at the same time, enough constraints should be known to be able to develop realistic alternatives.
how important are prototypes?
they are useful when a specific hypothesis needs to be tested. simple models can often facilitate learning sooner than a single, elaborately developed model.
how are partners compared?
compare references, the actual role in the project, the team, the methodology, the deliverables, and the support provided through implementation. also ask which specialized services need to be supplemented by external providers.
how are results documented?
decisions, options, open issues, and approvals should be documented in a way that allows for traceability. the format of the documentation must be appropriate for the subsequent development phase.
when are external specialists needed?
whenever the required expertise or formal responsibilities fall outside the agreed-upon scope of the design. these interfaces should be identified early on.
how to avoid unnecessary loops
through clear decision-making criteria, timely coordination among experts, and prototypes that specifically address the greatest uncertainties.
the perspective of f/p design
f/p design combines strategy, industrial design, and implementation-oriented development work across a variety of projects. you can find more of our work in the industrial-design-portfolio.
