What a fifteen-minute intake should capture before anyone opens a ticket

This briefing covers What a fifteen-minute intake should capture before anyone opens a ticket, written so every control in the blog editor is represented: italic emphasis, underline, strikethrough, inline code, H₂O and E=mc².

Read the public site at Speecto and the project notes collected for this story.

What the engagement covered

Teams usually arrive with a product that already works in one corner of the business and a backlog that has outgrown the original diagram. The useful first week is not a rewrite. It is a map of who uses the system, which numbers they trust, and which steps still depend on a spreadsheet. That map is what the rest of this article walks through, with the same sections we use on a live discovery.

Signals we look for first

• A single owner for the workflow, not a shared inbox.
• A number the team already reports, so the new screen can be checked against it.
• One path that fails in public more often than the rest.

Sequence we follow

1. Interview the people who close the loop, not only the people who requested the project.
2. Trace one real record from intake to the report a customer sees.
3. Write the constraints before choosing a stack.
4. Ship a thin slice that replaces the spreadsheet, then widen it.

Checklist before kickoff

• Access to production-like data, with personal fields removed.
  
• A named reviewer for copy and for the numbers.
  
• A date the current workaround must stay available until.
  

This paragraph is indented, the way a nested note sits under a decision in the editor.

This line is centered, using the alignment control from the toolbar.

The hardest part is not the interface. It is agreeing which version of the number is the one the company will stand behind.

Attachment

The upload below is the media attachment stored on the post. It is the same control as choosing a file from the editor’s upload button.

Media block

A media block can carry a caption. This one uses an image already in the library.

Embed / iframe

Embeds accept a YouTube or Vimeo URL, or a full iframe snippet. Only the address is kept. The player below is an iframe URL.

How this lands in delivery

After the map is agreed, engineering time goes to the thin slice: one role, one record, one report. Everything else stays on the old path until that slice matches the number the team already trusts. That is slower to describe than a full redesign and faster to put in front of a customer. The posts in this series each take one slice — onboarding, reporting, content, or the handoff between design and build — and show the same shape of work.

If you are comparing this with an internal brief, start from the checklist above and ignore the tooling until the owner, the number, and the failure path are written down. The editor on this post is here so the article itself exercises headings, lists, links, quote, rule, alignment, indent, upload, media, and embed together.

Related category

The relationship below points at a blog category already in the CMS.