Pattern 09 · Chat or assistant · Interaction pattern
Match recipe
Practice view. What to build, the words on screen and how to measure it. Switch to Research for why it should work, the framework properties and the references.Research view. The research side is shown below the card: why it should work, the properties it targets and the references. Switch to Practice to hide it.
Next to an open text field, a small recipe lists the five signals a good brief contains: problem, domain, expertise, context, outcome. As the user writes, each signal ticks when detected. Nothing is mandatory.
The user stays in chargeThe system shows how it worksCase: FORCIT Signal Studio (company approval pending)
Done right, done wrong
Schematic screens, not real products. Click a screen to enlarge it.In practice
FORCIT matches challenges to experts by comparing the wording of both, so the words in the description decide the match. Signal Studio holds twenty-six candidate patterns for the moment of writing; the match recipe is the lightest one: it leaves the field open and teaches while people type. A comparison with the structured brief and the guided conversation is the planned test.
Words on screen
Obligations to keep in mind (AI Act, GDPR)
- Remind people what they are sharing before it reaches third parties. (O3, IUI 2026, Table 1)
- Say that the recipe is guidance, not a requirement, and that an AI interprets the draft. (O1, IUI 2026, Table 1)
Design considerations, not legal advice or a conformity assessment. What O1 to O5 mean.
Build it
Illustrative signatures, not a published library: the names below are suggestions to adapt to your stack. Thresholds are examples to tune on your own data.
States: empty, writing, ready, submitted
Component: <MatchRecipe signals={[problem, domain, expertise, context, outcome]} text={draft} />
Prompt snippet: For each of the five signals, return detected, partial or missing, with a four-word hint for missing ones. Do not rewrite the user's text.
Output schema: { "signals": [{ "id": "string", "status": "detected | partial | missing", "hint": "string" }] }
Measure it
Same idea, other names
Applied by: nobody yet · Replicated by: nobody yet · Used this pattern? Tell us and get listed
Try it
Research side · why it should work
Why it should work
Properties targeted
Across contexts
| Context | Users | State | Result |
|---|---|---|---|
| FORCIT challenge brief | innovation managers | Seen in a case | pattern 01 of 26 in Signal Studio; user test to be scheduled |
| Your context | Bring your case |
Editors
Related patterns
All patterns
Pattern 05 · Dashboard with AI insights, Chat or assistantUrgency labels for prioritisationA small set of urgency levels on every item, so a full inbox can be scanned in seconds and the order of work is explicit.Seen in a case
Pattern 11 · Chat or assistantStaged conversation: the code decidesThe conversation always sits in one named phase. The model can only signal readiness; the app decides when to move on, refuse or repeat.Seen in a case
Pattern 08 · Dashboard with AI insightsReview a colleague's work checkpointAI-prepared work by a junior reaches a senior with the source, the junior's note and two clear actions.Seen in a case