Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.
Inventory of current practice systems and workarounds
Most practices run on a main system plus a quiet layer of spreadsheets, paper diaries, shared inboxes and sticky notes that nobody has written down. Listing every system, what it holds, who uses it and which workarounds exist around it shows what any new or improved software actually has to replace, and it is the starting point for every decision in this area.
First tasks
- List every login and subscription the practice pays for from the last bank statement
- Sit with reception for 30 minutes and note every spreadsheet or paper list they use
- Ask each professional which task the system makes them do twice
- Mark the three biggest gaps on the inventory and share it with the partners
Software requirements list from every role
Software chosen from a sales demo usually fits the owner and frustrates the front desk, or the reverse. A written requirements list, gathered from reception, billing, clinicians or fee earners and the practice manager, and split into must have and nice to have, turns a vague wish for better software into something every vendor can be scored against.
First tasks
- Send each role a short form asking for the five tasks they do most in the system
- Rewrite each answer as a testable requirement statement
- Hold a 45 minute session with the owners to rank must have against nice to have
- Mark the deal breakers in bold and date the final version
Software owner and decision group for the practice
When nobody owns the system, settings drift, updates are ignored and every staff complaint goes to whichever partner is nearest. Naming one system owner, a small decision group and a simple rule for who can change settings gives the software a steward, and stops changes being made on a busy afternoon without anyone knowing.
First tasks
- Ask who already fixes the system when it misbehaves and talk to them about the role
- Choose three or four people for the decision group across the main roles
- Write one paragraph on which settings changes need group approval
- Announce the system owner and the request route at the next staff meeting