First Product Build Brief

Step 1 of 4

Choose one company and one problem

For PMI, PepsiCo or another company already researched, select the existing report. Known facts will fill automatically. If no report is stored on this device, start a new brief and add only the essentials.

Do not repeat discovery, and do not guess.

This brief is for the single decision we could build and test first. It is not a company overview and it is not a request for every possible use case.

Existing Reliability Discovery report on this device If the list is empty, the earlier report was completed in another browser or device. Start a new brief and copy only the known facts.

Step 2 of 4

Define the decision

Describe what actually happens. Do not ask the customer to design our product. Stay with one recent episode and record the available choices.

The operating moment

Required before anything is built

What triggers the decision? coreThe first observable sign and the moment someone must decide what to do.

Who makes the decision today? coreUse a role, not necessarily a person’s name.

How quickly must they act?

What exact question must the product answer? core

What actions are genuinely available then? coreDo not add hypothetical actions that the team could not actually take.

Which actions require approval or are prohibited?

One comparable episode

Beginning, action and result

When does the episode begin?

When does it end?

What must be known before the action? core

What result must be observed, and after how long? core

Step 3 of 4

Map the evidence

Ask where facts are recorded, not whether they “have data”. A sample export and field dictionary are enough for the first technical check.

Source systems

Names and owners, not architecture diagrams

Where is the pre-action state recorded? core

Where is the action recorded?

Where is the result recorded?

What joins the records?

History and access

Unknown is a useful answer

How many comparable episodes exist?

Were different actions tried?

Can they share a small sample export? core

Who approves access?

What important facts exist only in people’s heads?

Only if named worker or other sensitive data may be involved

Does the first product need named worker data?

Step 4 of 4

Define the proof

The product must improve a real decision beyond today’s workflow. Name the incumbent, the remaining gap and the economic test.

What exists already

Do not rebuild a dashboard they own

How is the decision made today?

Which tools already help?

What simple baseline should Kalyr beat?

What decision remains unsupported after those tools have done their job? core

The first product

One surface, one user, one decision

Where should the result appear?

What evidence must appear beside it?

When should Kalyr ask for missing information?

When must it abstain or escalate?

Operational and economic acceptance

This is how we earn the next decision

Operational metric core

Who owns it?

How does improvement become money? core

Minimum result that would justify continued use

What commercial decision follows a successful shadow test?

Review

One build case, without the repetition

The brief can be sent while incomplete. Missing blockers remain visible, so Minara does not have to invent answers or delay sharing useful evidence.