Map the work first. Decide about software second.

Process Mapping Day for SMEs: Understand the Work Before You Buy Anything

We come to your site for half a day, follow the work from first contact through to the money landing, and write down how it actually flows. Then we tell you which parts need a system, which parts need a decision or a form or a conversation with a supplier, and which parts are fine as they are. The map is the product. You are buying our information, not a proposal.

Most software disappointments in small business are not software failures. They are a well built system dropped on top of a process that nobody had ever written down, with the result that the awkward bits get worked around exactly as they always were, only now inside a subscription. Mapping first is unfashionable and cheap. The day is quoted before it is booked, capacity is about one a fortnight, we drive to you across Melbourne, the south east corridor, Gippsland and Geelong, and the fee is credited against whatever you decide to build.

Book a Process Mapping Day (03) 9003 0111

Realistic ROI

4 to 5 hours

On your floor, following the actual work

Plus travel each way. We want the counter, the bench and the admin desk, not a boardroom with a whiteboard and a facilitator.

Process change first

Plenty of what a map turns up needs no software at all

We expect a meaningful share of any map to be a form, a handover or an approval that could be changed on Monday for nothing. Those go in the report even though they earn us nothing.

About one a fortnight

Is the capacity we hold

The visit plus writing the map properly is three days of work, and there is no junior analyst to send in our place. Expect the next date to sit a few weeks ahead.

100% credited

Against whatever gets built afterwards

If the map leads to a build with us, the day comes off the first invoice. If it leads nowhere, you owe nothing further and keep the document.

Four Reasons Mapping Comes Before Buying

None of these are new ideas. They are just the ones that get skipped when a demo looks impressive.

Nobody in the business has ever drawn the whole thing

Everybody knows their own segment perfectly and almost nobody has seen the full path from enquiry to paid invoice. That is not negligence, it is what happens when a business grows by adding people to the busiest point. The first genuine value of a mapping day is often simply that the owner and three staff look at one diagram together and disagree about it, which is a productive hour that never happens otherwise. Half the arguments in a small business are two people describing different parts of the same broken handover.

A good system on a bad process is an expensive way to keep the bad process

When a workflow has an unnecessary approval, a duplicate data entry or a step that exists because of a person who left three years ago, buying software does not remove it. It encodes it, gives it a login, and makes it harder to change. We have seen businesses pay a five figure implementation to automate a checking step that only existed because an upstream form asked the wrong question. Fix the form and the checking step disappears for nothing, which is a far better outcome and a far worse sale.

You cannot rank what you have not costed

Every business has a list of irritations, and the loudest one is rarely the most expensive. Mapping puts a rough annual figure against each step so the list can be sorted by money instead of by volume of complaint. That reordering is frequently the most useful part of the document, because it gives an owner a defensible reason to tell a valued and vocal staff member that their pet problem is genuinely third in line rather than being ignored.

The map is what makes a supplier quote comparable

Send three vendors a vague description and you get three quotes for three different jobs, none of which can be compared. Send them a current state map, a defined scope and the awkward cases written down, and the quotes become an actual comparison. This is true whether the eventual supplier is us, your existing IT provider or somebody you have not met yet, which is why the document has no strings attached to it. A map that only we can quote against would not be worth much to you.

How the Mapping Day Runs

We follow the work rather than interview people about it. There is no workshop and nobody comes off the tools.

A defined start and end

Agreeing the boundaries

Before the date we agree what we are mapping and where it starts and stops. Enquiry to invoice, or purchase order to despatch, or patient booking to claim. Vague scope produces a vague map, and a business with three distinct flows needs them named rather than blended into one diagram. This is also where we work out how many people we need to stand beside and whether half a day is genuinely enough or you are actually asking for a full one.

The physical route

Walking the path

The first hour is spent following the work in the order it happens rather than in the order it is described. Where the enquiry arrives, where it gets written down, who touches it next, where it waits, where it goes back. Waiting time is the thing most maps miss and it is usually the largest single number on the finished document. A job that takes twenty minutes of work and four days of elapsed time has a queue problem, not a speed problem, and those need completely different remedies.

The real steps, not the official ones

Sitting with the people

We watch three or four people do their actual work at their actual desks, asking as little as possible. Show me the last one you did beats describe your process every single time, because a real record still has the exceptions attached. The telling phrases are always the same: I just check that again here, it usually comes through twice, I keep my own spreadsheet because the system does not hold it. Each of those is a step that never appears on any official flowchart.

Numbers you can defend

Counting the touches

How many times one piece of information is typed. How many minutes a task took while we watched it, not how long people believe it takes. How many of the last fifty jobs needed a rework touch, and what caused it. Where a figure is an estimate we label it as an estimate and give the range. A map with confident invented numbers is worse than a map with honest ranges, because somebody will eventually check.

Corrections while we are still there

Playback before we leave

Twenty or thirty minutes at the end walking through what we saw, in plain language, with whoever is available. This is where you tell us that the step which looked absurd exists because of an insurer requirement or a customer who once sued somebody. That correction is worth more than another hour of observation, and it means the written map arrives as a confirmation rather than as an unwelcome surprise.

Current state, costed, and split

The written map, five days later

A current state flow diagram, a step by step table showing who does what and how long it takes, a ranked list of improvements with a rough annual cost of the status quo against each, and the split that matters most: which items are a process change, which are configuration of software you already own, which need something built, and which we recommend leaving alone. Yours outright, with no watermark and no proposal stapled to the back.

What a Mapping Day Typically Turns Up

Task	Traditional	Mapped first	Notes
The same detail typed three times	Accepted as normal	Counted and costed	Usually a system boundary nobody owns. Sometimes an integration, sometimes just one field turned on.
A checking step nobody can justify	Automated at great expense	Traced back to its cause	Often exists because an upstream form asks the wrong question. Fix the form and the step vanishes for nothing.
Four days of waiting inside a twenty minute job	Blamed on staff being slow	Identified as a queue	Queue problems and speed problems have opposite remedies. Buying faster software fixes neither.
The private spreadsheet	Discovered after go live	Found on the day, and understood	A shadow system is a specification. It shows exactly what the real system fails to hold.
An approval that is now ceremonial	Rebuilt faithfully in the new tool	Questioned before anything is built	Some approvals are legal or insurance driven and must stay. Many are a habit from a smaller business.
Two people who each think the other checks it	Surfaces as a customer complaint	Visible the moment it is drawn	Handover gaps are almost invisible from inside and obvious on a diagram.
Software you already pay for and barely use	A second product bought to fill the gap	Licence audit against the map	Common in regional businesses with capable systems whose setup was never finished.
The genuinely good bits	Rebuilt anyway because it is in scope	Named and left alone	A map that finds nothing worth keeping is a map written by somebody selling a replacement.

How Process Mapping Gets Wasted

Mapping the process you wish you had

The strongest pull in the room is towards documenting the intended process rather than the real one, because the real one is embarrassing and the intended one is what the induction manual says. A map of the intended process is worthless, since the intended process is not the thing costing you money. If a step is regularly skipped, or two people quietly do it differently, that belongs on the diagram in its actual form. We would rather draw an ugly accurate map than a tidy fictional one.

Producing a beautiful diagram nobody uses again

Process mapping has an unhappy history of large laminated wall charts that were correct for about six weeks. The defence is to keep the map at the level of decisions rather than keystrokes, and to attach numbers and owners to each step so it stays a working document rather than an artefact. If the diagram cannot be used to argue about priorities in a management meeting, it was drawn at the wrong altitude and it will be quietly recycled.

Treating every finding as a project

A good map produces more items than any small business can act on in a year, and the failure mode is attempting four at once. Two get half finished, one gets abandoned and the fourth gets blamed for the disruption of the other three. Take the top item, do it properly, let it settle for a month, then take the next. Sequencing is a genuine skill and it is the part most improvement programmes get wrong.

Mapping while a restructure is underway

If roles are about to change, or a system is mid migration, or a key person is on the way out, the map you get describes an operation that will not exist by the time the report lands. Wait until the dust settles, or accept up front that the deliverable is a snapshot with a short shelf life. We would rather tell you to postpone by two months than take the booking and hand you an accurate description of the past.

Using the map to build a case against a person

Occasionally a mapping day is quietly commissioned to produce evidence about an individual. It is a bad use of the instrument and a worse use of the money, because the moment staff sense it the observation becomes useless and the trust cost outlives the report. If there is a performance problem it needs a management conversation, not a consultant with a clipboard. We will decline the engagement if that turns out to be the brief.

Assuming the answer will be software

Plenty of clients arrive having already decided what they will buy and want the map as justification. That is a reasonable instinct and it sometimes turns out to be right, but it puts us in the position of validating a decision rather than testing it. If the honest finding is that a process change and a supplier conversation would deliver most of the benefit for a fraction of the cost, we will write that down, and you should be prepared for the possibility that the day talks you out of the purchase.

How Yes AI Runs a Process Mapping Day

We split the findings honestly

Every item on the map is tagged as a process change, a configuration of something you already own, a genuine build, or leave alone. The first two categories are usually the cheapest and fastest and they generate no work for us. Publishing that split is the point, because a report where every finding happens to require the author is not a report.

The map is yours without conditions

No watermark, no proposal appendix, nothing tying it to us. Take it to three suppliers and get comparable quotes for the first time. If somebody else builds it better or cheaper on the back of our document, you have still had the value you paid for.

We will tell you not to buy anything

Some operations are already running about as tight as their size allows, and the honest conclusion is that the two irritations you called about are worth less than the disruption of changing them. That makes for a short report and it is still the correct answer. Being paid for the day is exactly what makes it possible to say so.

The fee comes off the build

If the map leads to work with us, the day is credited in full against the first invoice, because charging twice to understand the same operation would be indefensible. If it leads nowhere, that is the end of it, with no follow up sequence and no quarterly check in you did not ask for.

From First Call to a Map You Can Quote Against

Five steps over roughly three weeks. Most of the elapsed time is diary, not effort.

A short call to define the boundaries

A 30-minute consultation agreeing which flow of work we are mapping and where it starts and ends, how many roles are involved, whether you sit inside the travel radius, and what the day costs. If mapping is the wrong instrument, we say so here.

Book a normal working day

Not the quiet one. We want the day where the schedule has to be reshuffled, because the exceptions are the expensive part. Nothing needs tidying beforehand and nobody needs to prepare a presentation.

Half a day following the work

The walk, the observation, the counting of touches and waits, then a plain spoken playback before we leave so you can correct anything we have misread while we are still in the building.

The written map, five business days later

Current state diagram, a step table with owners and durations, ranked improvements with a rough annual cost against each, and the four way split between process change, configuration, build and leave alone.

A half hour to argue with it, then your decision

We talk through the map and you push back. If you want a fixed price on one item, that becomes a separately scoped piece of work with the mapping day credited against it. If you want to take the map to somebody else, that is entirely fine.

FAQ

What is a process mapping day, exactly?

Somebody experienced spends about half a day at your premises following one flow of work from beginning to end, watching the people who perform it rather than interviewing them about it, and counting what can be counted. Five business days later you receive a written current state map: a flow diagram, a step table showing who does what and how long it takes, a ranked list of improvements with a rough annual cost of the current state against each, and a clear split between the items that need a process change, the items that need software you already own to be configured properly, the items that need something built, and the items we suggest leaving alone.

Why map first instead of just buying the software?

Because a well built system dropped onto an undocumented process encodes that process, including the parts that should not exist. The classic case is a manual checking step that only exists because an upstream form asks the wrong question. Automate it and you have paid to make a mistake permanent and harder to remove. Fix the form and the checking step disappears for nothing. Mapping first also makes vendor quotes comparable for the first time, because three suppliers pricing from the same defined scope are finally pricing the same job.

Do you only recommend things you can sell us?

No, and the structure of the report is designed to make that visible. Every finding is tagged as process change, configuration, build or leave alone, and we expect a solid share of the items to fall into the first two categories, which generate no work for us at all. Being paid for the day is precisely what makes that possible. A free assessment has to produce a sale to justify the consultant’s time, so its findings drift toward whatever that consultant happens to sell, and everybody in the room quietly knows it.

How much does it cost and is the fee credited?

The day is quoted before it is booked, after a short call to confirm scope, number of sites and roles, and travel. You get the number on that call rather than after the visit, and there is no hourly meter running afterwards and no travel surcharge buried in it. If the map leads to a build with us, the fee is credited in full against the first invoice, because charging twice to understand the same operation would be hard to defend. If it leads nowhere, you owe nothing further and the map is still yours.

Where do you travel for these?

Melbourne, the south east growth corridor including Dandenong, Berwick, Narre Warren, Cranbourne, Clyde, Officer and Pakenham, West and Central Gippsland covering Warragul, Drouin, Moe, Morwell, Traralgon and out to roughly Sale, and Geelong with the Bellarine and Surf Coast. That is the published radius and we would rather state it than imply national coverage we cannot deliver. Beyond about two hours drive the exercise stops being a half day and starts carrying travel that distorts the value. If you are outside the band, ask, and you will get a straight answer rather than a hidden surcharge.

How many people from our team need to be involved?

Fewer than you would expect, which is the main advantage of mapping by observation instead of by workshop. We want thirty minutes with whoever owns the process at the start, three or four people doing their actual jobs while we watch, and whoever is available for the playback at the end. Nobody comes off the tools for a day, nobody prepares a presentation, and the business keeps running. If you would rather run a facilitated workshop with the whole team in a room, that is a legitimate approach and there are consultants who do it well. It is simply not this product.

When is a mapping day a bad idea?

When a restructure, a system migration or a key departure is already in motion, because the map will describe an operation that no longer exists by the time you read it. When you already know precisely what you want built and have written it down, in which case you need scoping and a quote rather than an observation. When money is genuinely tight, since the immediate problem deserves the spend more than a document about the medium term. And when the real issue is a person or a management decision rather than a process, because an outsider with a clipboard will not fix that and can make it noticeably worse. We would rather turn the booking down on a fifteen minute call than take it and disappoint you on the day.

Draw the Work Before You Buy the Software

Book a short call. We will agree what would be mapped, confirm whether you sit inside the travel radius, and tell you what the day costs. If mapping is the wrong instrument for your question, you will hear that on the call rather than after the invoice.