Lunnoa (public demo) · Lunnoa Reports, a tour of the building blocks
What a workshop deliverable looks like
Section 02

Current state

A typical workshop report opens each section with a one-paragraph lead, then supports it with findings, direct quotes, and callouts. This section demonstrates that pattern with illustrative content.

Key findingHigh impact

Manual handoffs multiply the time a routine task takes

In a typical process discovery workshop, a single request can pass through four or five inboxes before it is resolved. Each handover is a manual email or shared inbox forward, and each one adds a delay that nobody owns.

We do the same five-step approval on every request. The five steps make sense. Doing them all by hand, five hundred times a month, does not.

Alex Example, Operations Manager
Key findingMedium impact

The data needed to automate a process already exists, just not in one place

Workshops repeatedly surface the same pattern: the fields needed for a decision are already captured somewhere in the stack. The gap is integration and ownership, not data capture.

Nobody signed off on this process existing this way. It grew one exception at a time.

Jordan Example, Finance Lead

Every team has its own spreadsheet version of the truth. We reconcile three of them every Friday.

Sam Example, IT Director
Today (manual, illustrative)
  • Request arrives by email, forwarded to a shared inbox.
  • A coordinator opens the request and retypes key fields into the system of record.
  • A second person checks the entry before it is actioned.
After automation (illustrative)
  • A Lunnoa agent receives the request and extracts the key fields automatically.
  • Matching and validation run without manual re-keying.
  • Exceptions route to a queue for a person to review, not the whole volume.

Workshop participants
Alex Example
Operations Manager · Operations
Interviewee