Y Not YouAI & Automation
Why Your Automation Keeps Failing (and the Fix)
Our own content shoot automation was failing 60% of the time, and a smarter version of the same workflow would not have fixed it. Here is what was actually wrong, why we moved the decision to where our client data lives, and how match accuracy went from 40% to 99%.
Key takeaways
- Automation fails when it can’t see the data. Ours was asked to match shoots to clients without access to the client records.
- The fix is where the decision happens, not a smarter tool. We moved the matching into the workspace that holds the customer data.
- Give each tool one job. One tool now carries the raw data; the system with the context makes the call.
- Build in a human backstop. Retries run first, then a person is flagged by name, so no shoot slips through.
- The result: 40% to 99% match accuracy. 50+ shoots a month, 12 to 16 hours saved every month.
When an automation keeps getting things wrong, the usual instinct is to make it smarter: add rules, add steps, add AI. Sometimes that works. Often the problem is somewhere else entirely: the automation is being asked to make a decision it can’t see enough to make.
This is a story from our own operations at Y Not You. We run 50+ content shoots a month, and an automation that was meant to file each one under the right client was failing more often than it worked. Here is how we found the real cause, what we changed, and the question to ask the next time one of your own automations keeps breaking.
The job: match every shoot to the right client
Every content shoot we run has to be matched to the right client record. That sounds simple until you see where the details lived: a calendar, file storage and a spreadsheet, three places that didn’t talk to each other.
An earlier automation was trying to make the match. It failed 60% of the time. Each failure left a shoot to be sorted out by hand, and at 50+ shoots a month that adds up.
Why the automation kept failing
The failures weren’t random, and they weren’t a matter of a few bad rules. When we traced them to their cause, the pattern was clear: the matching was happening in a tool that could not see the customer data.
This is the part most businesses miss. When an automation fails, it is natural to tune the automation. But if the information it needs sits in another system, every improvement is still guessing. The question to ask is not “how do we make this smarter?” but “where does the information to make this decision live?”
Put the decision where the data lives
Our client records live in our project workspace. The shoot details were being carried by a separate workflow tool, which had no view of those records. So we flipped the setup around:
- Move the decisionWe built a custom AI agent inside the workspace that holds our client records. It matches each shoot on company name and point of contact, even when the details don’t line up exactly.
- Give the carrier one jobWe cut the workflow automation back to one task: carrying the raw shoot data into the workspace. No AI work is done outside it.
- Retry before escalatingIf a match doesn’t go through, the system retries automatically.
- Flag a person by nameIf retries don’t resolve it, a step flags a named person to review the shoot, so nothing slips through without a human look.
In short: one tool moves the data, and the system that holds the context makes the call.
Why matching “close enough” matters
Real data is messy. A company name gets typed one way on the calendar and another way in the spreadsheet; a contact’s name is shortened or misspelled. A rigid matching rule fails on all of those. That is why the agent matches on company name and point of contact even when the details don’t line up exactly, and why it needs to see the full client records to do it.
What changed
Shoot data that used to be split across three places now lands on the right client record with near-zero manual intervention. And no shoot falls through: retries run first, then a person is flagged to review it. That is 12 to 16 hours back every month.
How to diagnose your own failing automation
If one of your automations keeps getting things wrong, work through these before you add more steps to it:
- List what it gets wrongLook at the failures together, not one at a time. A pattern usually shows up.
- Ask what it would need to knowFor each failure, what information would a person have used to get it right?
- Find where that information livesIf it sits in a system the automation can’t see, that is your answer. Tuning the automation won’t fix it.
- Move the decision thereLet the system with the context make the call, and keep the other tool to carrying data.
- Keep a human backstopRetries first, then a named person, so nothing disappears quietly.
Not every problem needs AI to solve it; some need a plain rule in the right place. If you are weighing the two, AI vs. automation: when to use each walks through the difference. For a broader look at where AI belongs in your business, see our AI & Automation advisory.
Put the intelligence where the data lives
When automation fails because it can’t see your information, the fix isn’t a smarter tool. It’s moving the decision to where the information already exists. That one change took our matching from 40% to 99%, and it applies well beyond content shoots: any time a tool is guessing, ask where the answer actually lives.
Is your automation guessing?
Every engagement gets all three Y Not You partners. Show us where your automation breaks and we will find where the decision belongs.
For owners anywhere
The Business Collective
Group-scale access to all three Y Not You partners: a daily knowledge tip, a weekly open-forum call, a monthly networking call, and a quarterly guest speaker.
Join The Business Collective