Do-it-yourself discovery canvas

Map one request, one exception, and one accepted result.

You do not need a finished specification. Use this page to collect enough operational truth for a focused first conversation without sending passwords, private records, production exports, or unredacted personal data.

Canvas

Write the workflow in the order people experience it.

A useful example can be fictionalised or redacted as long as it preserves the roles, decisions, systems, and failure path. Estimate ranges when exact counts are not available and label assumptions.

StepWhat to captureOwner

Trigger

EventChannelVolume range

Requester

Triage

Required fieldsCategoryFirst owner

Operations

Decide

RuleAuthorityDeadline

Approver

Fail

ExceptionEscalationEvidence

Named role

Close

AcceptanceRecordNext owner

Business

Current tools

Name the systems, spreadsheets, chat channels, email inboxes, documents, and manual workarounds involved. Identify the current system of record if one exists.

Roles, not names

List requester, reviewer, approver, performer, administrator, auditor, and support owner. Note where one person currently fills several roles.

The difficult exception

Choose one recurring case: missing information, duplicate entry, late approval, unavailable owner, provider timeout, rejected work, or record mismatch.

Acceptance proof

Describe what an authorised person should be able to observe when the workflow is complete and trustworthy.

Safe to include initially

Role labels and approximate team shape
Redacted or synthetic workflow examples
Software product names and integration questions
Approximate frequency and delay ranges
Known business and technical constraints

Keep out of the first email

Passwords, API keys, private keys, or recovery codes
Unredacted customer, employee, patient, or financial records
Production database dumps or access tokens
Payment-card or government identity details
Anything your organisation has not authorised you to disclose

Subject line

Philippines workflow discovery — [short process name]

In the message, include: the trigger; roles; current tools; the most costly exception; desired acceptance proof; known privacy, payment, procurement, or support constraints; and who may authorise a discovery.

Send the canvas

Direct contact, no web form.

This site intentionally uses email and phone instead of collecting project details through a public form.

faithforgelabsllc@gmail.com +1 502-442-2082

Before sending

Authorised contact named

Examples redacted

Remote-delivery expectations stated

Unresolved adviser questions labelled