Hiring managers in healthcare operations keep describing the same gap. Plenty of candidates can propose an improvement; far fewer can show what the situation looked like before they touched it. If you work, or want to work, in a cardiology practice’s administration, quality or patient-services team, the ability to capture a baseline is one of the most portable skills you can build. This article sets out what the skill involves, how to practise it on non-clinical processes and how to describe it on a CV. It addresses administrative work only. Clinical judgement belongs to clinicians and is outside the scope of what follows.
What “capturing a baseline” means as a professional skill
A baseline is a dated, method-stamped description of how a process performs today: its steps, its elapsed times, its effort and the themes in what people say about it. As a competency, it breaks into four parts. First, scoping: choosing a process small enough to describe, such as how a new enquiry becomes a booked appointment. Second, measurement: picking observable quantities such as hand-offs, waiting time between stages and repeat requests. Third, recording: keeping the data in a form someone else can reread a year later. Fourth, restraint: leaving the process alone while you record it.
Each part is trainable, and each is visible to an interviewer. Of the four, restraint is the rarest. Most people instinctively fix problems as they find them, and the discipline of observing first is what distinguishes an analyst from a firefighter.
Skills that sit around it
- Process mapping. Drawing the real route a file takes, by speaking to the people who handle it instead of copying the policy document.
- Sampling. Choosing a representative stretch, noting the conditions and avoiding the pull of the most memorable cases.
- Light data handling. A spreadsheet is enough. What matters is clean dates, consistent units and a note describing how each column was filled.
- Qualitative coding. Sorting free-text feedback into a few administrative themes without reading personal details into them.
- Plain reporting. Presenting a before picture on one page that a non-specialist can follow.
How to practise without waiting for a project
Nobody has to grant you permission to build this habit. Choose a small, harmless process within your own remit and record it for two weeks.
- Pick a narrow question. For example, how long does a returned form take to be logged?
- Write the steps. List each stage and who is involved.
- Time a sample. Note when each stage starts and finishes for about a dozen items.
- Record the conditions. Staff on leave, month-end pressure and unusual volumes all belong in a notes column.
- Summarise on a page. Typical value, longest value, count of repeats, and two or three observations.
- Repeat later. After you or your team change something, run the same sample the same way.
The finished pair of one-page summaries is portfolio material. Remove anything identifying and it can be shown in an interview.
Learning from adjacent fields
Engineering teams have a long habit of measuring before optimising, and reading how they frame it can help you borrow vocabulary. The group behind the technology pieces on this blog has described how engineering discipline shapes its digital work in India, and the idea of a recorded starting point appears in much of that culture. Clinical sites like this one also publish structured reference pages; the series on how the functional class system is defined in cardiology is an example of consistent, repeatable categories. Administrative baselines benefit from the same consistency: define each category before you count.
Where international enquiries add a layer
Roles in cardiac care operations increasingly involve overseas enquiries, and it helps to know how those families research. The BestEyeHospitals resource for international patients is a directory and planning site, and its published disclaimer states that its pages are for general information and that users should not delay seeking professional care on account of them. For a coordinator, the lesson is professional rather than clinical: patients arrive with pre-formed expectations, and a baseline of your own enquiry handling tells you how far your service matches them.
Describing the skill to employers
Be concrete. A line such as “documented the end-to-end enquiry process, sampled response times across three channels and presented a one-page baseline to the operations lead” says more than “improved processes”. If you later made a change, add the outcome measured against the same sample. Where you cannot share figures, describe the method.
In interviews, expect the question “How would you know it worked?” Answer it before you are asked. Explain that you record the current state first, agree the measure in advance, change one thing and repeat the sample in comparable conditions. Admit the limits too: seasonality, mix of enquiries and small samples all affect confidence. Interviewers value candidates who volunteer caveats because it signals that the person will not oversell a result later.
Seniority and the same technique
An entry-level coordinator shows the skill by recording a single process cleanly and handing over a tidy sheet. A team lead shows it by insisting that any proposed change names the measure it will be judged on, taken from a dated before record. A manager shows it by protecting the recording period from well-meaning tinkering and by presenting results with their caveats attached. The technique is identical at every level; what grows is the scope of the process and the confidence with which you defend the method to people who would rather skip it.
Common pitfalls for early-career analysts
Three errors turn up repeatedly. The first is recording too many variables, which makes the sheet unreadable. The second is failing to freeze the process during the recording period. The third is treating the baseline as a one-off document rather than a reference that should be dated, filed and found again. Avoid those and your work will already stand out.
A study plan for the next month
Week one: map one process. Week two: time a sample and note conditions. Week three: gather and theme feedback comments. Week four: write the one-page summary and ask a colleague to read it cold. If they can explain your starting picture back to you in a minute, the document works. Keep it, because the next time someone proposes a change at work, you will be the person who already knows how to ask for a before measurement, and that reputation travels with you from team to team.
