Describe the current work
Explain how it is done today, who uses the result and what is hardest. A complete specification is not needed on day one.
APPROACH / FLY
Get one piece of work right.
From the scope of the problem to ongoing upkeep, leave a basis that can be checked and used.
From discussion to use
Agree the scope
Confirm inputs, access, deliverables and checks. Identify third-party accounts, subscriptions and hardware separately.
Try and review
Use representative inputs and record the cases that do not fit. Obtain approval before writes or external actions.
Hand over for continued use
Transfer agreed files, configuration and instructions, including ownership of updates, records and exceptions.
Treat data access and actions separately
- Use the minimum material firstRedacted indexes, examples and field definitions can support the first discussion.
- Keep credentials out of the briefPasswords, tokens and administrative access need a separately agreed process.
- A draft is not an approvalSuggestions, record changes and sending are distinct actions.
- Access needs an end pointWhen a pilot ends or changes scope, review the material held and the access granted.
BEFORE WE BEGIN
A few useful answers
Do we need to buy a platform first?
No. Review the existing material and working method before choosing current tools, lightweight software or an external platform.
Can the first project be small?
Start with document organisation, one recurring workflow or an application study, with a defined scope and review method.
START WITH SOMETHING SPECIFIC