Every hospital runs on systems most visitors never see: appointment calendars, records software, billing screens, messaging tools. When one of those systems changes, a project team has to plan the change, and that plan is full of beliefs. This beginner primer tells the story of an imaginary hospital IT coordinator learning to write those beliefs down, and builds a mini-glossary along the way. It is about healthcare IT projects in the administrative sense only; nothing here is clinical or a recommendation for any patient.
The coordinator’s first big project
Our imagined coordinator, newly responsible for an upgrade to the outpatient scheduling system, arrived with a thick binder of requirements and a calendar full of meetings. The project plan looked complete. What it lacked, the coordinator realised during a late evening of reading, was any mention of what the plan was relying on. A cheerful sentence such as “the new screens will be ready for training in the third week” rested on at least five unspoken beliefs.
That evening, the coordinator started a plain page headed “What we are assuming”. By morning it held twenty lines. The glossary below grew out of the questions that page raised.
Mini-glossary for beginners
- Assumption: a belief the plan depends on that has not yet been confirmed. For example, “the vendor’s test copy matches what we run today”.
- Requirement: something the system must do, agreed in writing. Requirements are different from assumptions; one says what is needed, the other says what we hope is true.
- Dependency: another team, system or deadline that your work waits on. Dependencies are a rich source of assumptions, because you rarely control them.
- Test environment: a safe copy of a system used to try changes before they affect real work. Beliefs about how closely it matches the live system are worth writing down.
- Go-live: the day a change starts to be used for real. Plans around it contain many beliefs about timing and staffing.
- Stakeholder: anyone affected by or responsible for the change, from front-desk staff to finance.
- Owner: the role responsible for checking a specific assumption by a given date.
Turning the twenty lines into a usable page
The coordinator grouped the lines under four headings: people, data, systems and timing. Under people went beliefs such as “the department leads can attend training in the planned week”. Under data, “the existing appointment records are clean enough to move”. Under systems, “the new tool can talk to the billing screen without extra work”. Under timing, “the supplier’s delivery date will hold”.
Next to each line the coordinator added a short confidence word and the cheapest check. Most checks were conversations. A few required a request to another team. One required a small test, run on the test environment, to see how the old and new systems would exchange data.
The surprise in the data line
The belief about clean records turned out to be the shakiest. A short sample review showed duplicate entries and inconsistent formats, enough to slow the move. Because the problem surfaced weeks before go-live rather than on the day, the team added a clean-up step and shifted the training date. That was the moment the page earned its keep.
The dependency that nobody owned
Another line on the coordinator’s page read: “The supplier will deliver the training materials before the training week.” The check was a short email asking when the materials would arrive. The reply was vague. Followed up by phone, it turned out that the supplier assumed the hospital would write its own local screens and guides, while the hospital assumed the supplier would. Two parties each held a reasonable belief, and the two beliefs contradicted each other.
Left unsaid, that gap would have appeared on the first morning of training, when twenty staff members sat down with no guide. Because the page forced the question early, the coordinator arranged a joint working session, divided the writing and put owners’ roles beside each part. This is a good example of how a dependency, which the project does not control, is turned into an agreement.
A sample page, shortened
To show the shape, here is a trimmed version of what such a page might hold in its first week.
- People: department leads are free for training in the planned week. Confidence: hoped for. Check: ask each lead for dates. Owner: the coordinator. Due: this Friday.
- Data: old appointment records can move without manual repair. Confidence: hoped for. Check: review a sample with the records team. Due: next Wednesday.
- Systems: the billing screen keeps working with the new scheduler. Confidence: probable. Check: run a test on the test environment. Owner: the IT analyst.
- Timing: the supplier’s delivery date holds. Confidence: probable. Check: ask for written confirmation of the date.
Notice that nothing on the page is technical jargon. A department lead could read it and know what is being asked of them. That readability is the whole reason the format works across professions.
Questions beginners often ask
Is this the same as a risk register? They overlap, but a risk register lists things that could go wrong, while an assumptions page lists things you are counting on being right. Many risks begin life as a doubtful assumption, so the two documents feed one another.
Who should see the page? Everyone who has a line on it, plus the sponsor of the project. A hidden list helps no one.
How long should it be? Long enough to cover the four headings and short enough to review in ten minutes. If it grows beyond that, split it by team.
How to start your own page
- Write the change in one sentence.
- List the people, data, systems and timing it depends on.
- For each, write what you are assuming, in a full sentence.
- Rate each as confirmed, probable or hoped for.
- Pick a small check for each hoped-for line and give it a responsible role plus a due day.
- Look the page over every week until go-live.
Keeping the page alive after go-live
The coordinator did not retire the page once the new system was running. A short section was added for the weeks that follow go-live: beliefs about how many calls the help desk would receive, how quickly staff would adapt, and whether the reports finance relied on still looked right. Several of those guesses were wrong in small ways, and each correction fed the next upgrade. By keeping the page, the team built a modest institutional memory that did not depend on any one person remaining in the role.
The same instinct at household scale
Nothing about the method is specific to hospitals. Our article on a monthly money routine for students using an expense tracker shows the same instinct at household scale: say what you expect, then check it against what actually happens.
For context on the public face of such services, a general look at how remote consultation services are described in plain terms offers context. It is not health advice.
A signpost for IT learners
Some readers of this primer are beginners in IT itself. For them, a training site run from India, which describes courses geared to certification alongside consulting and other help for IT workers is one place to explore further. We mention it simply as a pointer.
What the coordinator would tell a newcomer
Asked years later what had helped most, the coordinator said it was not any tool but the habit of saying aloud what everyone was quietly counting on. The list did not make the project perfect. It made surprises smaller and earlier, which is all a good plan can ask for. If you are about to take on a first project of your own, begin with a blank page and the words “we are assuming”.
