corey.consulting

Field Guide · No. 01

Before you buy another tool.

You can't solve what you can't see.

A field guide to instrumenting your business before you buy another platform, automate another workflow, or sit through another demo.

01 — THE THREE IDEAS, IN ORDER

Every operator hits these walls in the same order.

The walls get more expensive the later you hit them.

A

You can't solve what you can't see.

The issues you fix are the ones you notice. Most teams populate their problem list from memory, gut feel, and whoever spoke loudest in the last meeting — not from measurement. The waste that isn't visible doesn't get solved.

B

The tool is downstream of the method.

Every expensive platform promises to replace methodology with features. None of them do. The teams that get the most out of Monday.com are the same teams that would get the most out of Salesforce — the value was never in the platform. It was in knowing what they needed to see.

C

Automation doesn't equal scalability.

Clean process unlocks scale. Automation just scales whatever you pointed it at. I've watched this at the $100M level in retail media, where automated reporting pipelines produced a more confident version of the wrong answer every month — because the process underneath had never been cleaned up.

Based on a case study

Measuring before buying — in the field.

How I helped a regional cell-tower operator cut more than 10,000 labor hours a year out of their 5G rollout — by measuring the waste, killing the bottlenecks, and moving the slow work off-site.

Read the case study

02 — BEFORE THE NEXT DEMO

Three questions to ask before you buy a tool.

Run these before the next platform demo. If you can't answer them, the demo is premature.

Q 01

What decision am I trying to make that I can't make today?

Q 02

What would I need to see to make it?

Q 03

What's the smallest, cheapest thing that could show me that?

Nine times out of ten, the answer to the third question is something you already own. Two custom fields on a Monday.com board. A timestamp column in a spreadsheet. Milestone tracking in Asana. The tool isn't the constraint. The method is.

03 — THE FOUR-FIELD TEMPLATE

Log these four things every time it runs.

For any recurring process in your business. Use whatever tracking system you already have.

Field
What to capture
Start
When the work actually began — not when it was scheduled.
Mile­stones
Two or three natural checkpoints in the middle of the process.
End
When the work was actually done.
Blocker note
One line if anything stalled, even if it cleared up on its own.

Run it for two to four weeks. Not forever. Just long enough to get a shape.

04 — AFTER TWO WEEKS

What to look for in the data.

  1. 01

    Which step takes the most time? Usually not what your team would have guessed.

  2. 02

    Which step has the highest variance? Consistent steps are rarely the problem. Variance is where the waste lives.

  3. 03

    What shows up most often in the blocker notes? That's your issues list, already written for you.

05 — BEFORE YOU AUTOMATE

Three diagnostic checks.

If the answer to any of these is no, automation will make things worse. Automating a messy process doesn't clean it up — it scales the mess, in ways that are harder to see and more expensive to unwind.

  1. 01

    Can you describe the process end-to-end without mentioning the tool?

  2. 02

    Could a new hire run it correctly from the description alone?

  3. 03

    Is the data it produces trustworthy enough to make a decision from?

A note on simpler tools

Simpler tools don't lose functionality. They require you to be more honest about what you actually need from them. That honesty is the whole job.

06 — TWO WEEKS OF REAL DATA

Run it this week.

  1. 01

    Pick one recurring process — not your biggest problem, your most repeated one. Runs at least 5× a week.

  2. 02

    Add the four fields to wherever you already track that work. No new tool.

  3. 03

    Tell your team it's temporary — two weeks — and that the data will decide whether to keep it.

  4. 04

    Run the process as normal. Capture the fields every time it runs.

  5. 05

    At the two-week mark, run the three data questions against what you collected.

  6. 06

    Bring the most interesting finding to your next team meeting as a new issue to discuss.

Let's see if this fits.

Send me a message and tell me what you're dealing with. One conversation is usually enough to know if I'm the right fit — and if I'm not, I'll usually know someone who is.