Sales & growth · Concept

Give a good conversation a next step.

A useful discovery meeting produces needs, constraints, and unanswered questions. A project brief should preserve all three.

The problem worth solving

Teams leave a meeting with different interpretations. A polished proposal can hide an assumption that nobody actually agreed to.

What the workflow could do

Prepare a draft from approved notes: goals, requirements, constraints, proposed next steps, and unresolved questions. Link important requirements to the relevant note. Explicitly distinguish what was said from what the team is proposing.

A first pilot

Have the meeting owner compare several drafts with the original notes. Check omitted requirements, invented commitments, and correction effort. Confirm the brief with the customer before converting assumptions into scope.

The business angle

This can be an internal capability or a specialized service for organizations with repeated discovery work. The useful outcome is clarity before work begins.

The useful question

Make it testable.

Does the brief reduce ambiguity without creating commitments nobody made?

Further reading

OpenAI · Evaluation best practices

These resources inform the implementation approach. The business concepts and pilot suggestions are original editorial starting points.

Explore more ideasFind your starting point

Find something useful.