In shaping sessions, we aim to collaboratively define the project scope, allowing for flexibility in execution while keeping the end goal in sight.

The output of a shaping session should be a clear understanding of the project, including key components and user flows, rather than detailed specifications or mockups.

It's important to clarify what the problem is before moving into shaping, as this links to product strategy.

Storyboarding the ideal vision of a product using simple tools can help teams visualize what they want to achieve without constraints, making it easier to solve significant customer problems.

In shaping sessions, we need to invite the right people to ensure we can make decisions quickly and effectively.

It's crucial to involve engineers in the shaping process to ensure that the project is feasible and to identify potential challenges early on.

When we give form to an abstract idea, it galvanizes the entire team and provides focus, even if the initial object doesn't become the final design.

The best design outcomes come from having a clear vision and understanding of what you're trying to achieve before involving designers in the process.

When shaping a project, we focus on what we can realistically achieve within our time budget, allowing for meaningful progress without overextending ourselves.