Who is trying to finish the work?
Name the user, role, Australian operating location, device and access needs.
Project brief / field note 10
Bring the operating problem. Build the brief together.
Use the prompts below to organise what you know, then call, email, or send the short project form. Unknown answers are fine; the first goal is to understand the problem clearly enough to choose a useful next step.
The ten-question brief
A clear starting packet.
Copy these headings into an email. Short, factual answers are more useful than a polished proposal.
What starts the journey?
A request, order, document, event, deadline or status change.
What proves completion?
Name the record, message, approval, payment or state that counts as done.
Where does it break now?
Describe delay, duplicate work, missing state, risk or an unavailable system—not just “manual”.
What owns the truth?
List current applications, spreadsheets, files, vendors and access owners.
What cannot be lost?
Data, URLs, rules, uptime, analytics identity, audit history or familiar staff workflow.
Which people and records are involved?
Note sensitive fields, vendors, access, retention, AI use and incident ownership.
Does value change hands?
Name seller, customer, currency, provider, receipts, refunds and tax/accounting owner.
Where and when does the work operate?
Provide Australian city, US/client collaborators, deadline, live windows and release/support ownership.
Which conclusions need another owner?
Flag legal, tax, privacy, accessibility, security, language or regulated-industry review.
Example structure
One paragraph can be enough.
Use this pattern without inventing facts:
Person + task
“Our [role] in [Australian location] needs to complete [task] using [current tools].”
Failure + impact
“The process currently fails at [handoff] and creates [specific delay, risk or duplicate work].”
Preserve + outcome
“We must preserve [data/system/URL/rule]. We would consider the first improvement successful when [observable evidence].”
Owners + timing
“[Name/role] can make decisions. Our target date is [date], and [owner] handles specialist conclusions and production release.”
What happens next
Discovery before prescription.
A first conversation is for fit and evidence, not a guaranteed scope or result.
Clarify the journey
Identify the real user, failure, system of record and owner.
Inspect available evidence
Review current system behaviour, access, source, data and vendor constraints where authorised.
Propose the smallest coherent move
Define target, exclusions, acceptance, backup, rollback, verification and measurement.
Direct contact
Send what you know.
Faith Forge Labs is based in the United States. Use the verified form, phone, or email; choose the contact path that fits your project.