Friday Triage in Berlin: Notes to Tickets Before 4 PM

1. Open the notes from the Berlin payments meeting

Start with the raw material you already have: a transcript, shared notes, chat messages, or your own shorthand. Do not clean everything up before using the assistant. Useful signals often hide in fragments such as “retry later,” “mobile users only,” or “someone from platform should check this.”

Paste the notes into a new assistant session and add the date, project name, and meeting participants if those details affect ownership. Remove passwords, access tokens, customer names, and private data before sending the text anywhere.

2. Tell the assistant what a useful ticket must contain

Give the assistant a fixed output contract. For example: “Turn these meeting notes into engineering tickets. For each ticket, provide a short title, context, user impact, proposed scope, acceptance criteria, dependencies, owner suggestion, priority suggestion, and open questions. Separate confirmed facts from assumptions. Do not invent technical details.”

This instruction gives the assistant a job that is narrower than summarization. A summary describes the meeting. A ticket helps a teammate decide what to build, investigate, or clarify next.

3. Ask for candidate tickets before asking for polished tickets

Use a two-pass workflow. First ask the assistant to identify candidate work items and group duplicate requests. Tell it to preserve unresolved issues as questions instead of turning every comment into a task.

• Candidate 1: investigate duplicate payment callbacks after a timeout.
• Candidate 2: add a visible retry state to the mobile checkout.
• Candidate 3: confirm whether the finance export needs a new field.

Review this list yourself. Combine items that belong in one delivery, split items that require different owners, and delete ideas that were mentioned only as speculation. This short review prevents a meeting full of possibilities from becoming a backlog full of accidental commitments.

4. Turn one approved candidate into a ticket

Choose the first item and ask for a complete draft. Include the team’s preferred format in the prompt. A practical ticket might begin with the problem, explain who is affected, and define the smallest useful result.

For the callback issue, ask for acceptance criteria such as: repeated callbacks do not create two successful payment records; retries remain observable in logs; existing successful payments keep their current behavior; and a test covers the timeout sequence. The assistant can propose wording, but the team still decides whether each criterion is correct.

5. Make uncertainty visible in the ticket

Ask the assistant to add an “Open questions” section when the notes do not answer something important. Good questions expose decisions that would otherwise block implementation: Which service owns the idempotency key? How long should a retry remain valid? Does the support team need a dashboard change?

Also ask it to label guesses. “Suggested owner: payments platform” is useful. “Owner: payments platform” is misleading unless someone actually agreed to it in the meeting.

6. Check the draft against the source notes

Paste the proposed ticket back with the original notes and ask: “List every statement in this ticket that is unsupported, ambiguous, or stronger than the notes.” Read the result line by line. Pay close attention to numbers, deadlines, customer impact, and phrases such as “all users” or “must.” Those details are easy for an assistant to overstate.

If your team already uses a standard ticket template, keep the final text compact enough to scan during planning. A ticket should help someone act without forcing them to reread a forty-minute conversation.

7. Send the reviewed tickets into your work tracker

Copy only the approved fields into Jira, Linear, GitHub Issues, or your internal tracker. Add the real owner, project label, priority, and due date yourself unless the meeting explicitly settled them. Link the meeting notes so future readers can inspect the source.

For teams that need a model connection, RelayVano provides pay-as-you-go access through an OpenAI-compatible API at https://api.relayvano.com. You can route this workflow through a model such as Claude Sonnet 5.5 and keep the same prompt structure while your team evaluates quality and cost.

8. Sign up once the desk workflow is ready

Sign up for RelayVano when you want to run the meeting-to-ticket workflow with your preferred assistant setup. Start with one recurring meeting, compare the generated drafts with tickets written manually, and refine the output contract after each planning session.