// ENGAGEMENT EXAMPLES
What an engagement could involve.
A spreadsheet has become the team’s main application. A role change has left approvals and access out of step. New software is live, but staff still rely on old trackers. These examples show how such requirements could be approached.
These are hypothetical scenarios showing potential approaches and deliverables. They do not describe completed client projects or achieved results.
Explore the examples
Hypothetical: Replacing a shared spreadsheet with a working application
Requests live in a shared spreadsheet that nobody fully trusts. See how scope, approvals, permissions, data migration, acceptance and support could be agreed before development begins.
Read the spreadsheet example EXAMPLE · ROLE CHANGESHypothetical: A team changes roles. Its approvals and access need to follow.
A new manager starts, but approval rights, open requests, records and application access still point to the old arrangement. See what would change, who signs it off and how it could be checked.
Read the role-change example EXAMPLE · SOFTWARE ADOPTIONHypothetical: A new application is live. The team needs to make it part of the work.
The new application is live, yet staff still keep their own trackers. See how role-based practice, task guides, configuration fixes and a support route could make it part of the daily work.
Read the software adoption exampleDiscuss your situation.
Tell us how the process works today, where it gets stuck and what needs to change. In a first discussion we’ll work out which capabilities apply.