Millicent Yedwa — AI & Automations Specialist

What this says about me

I notice when context keeps being rebuilt by hand.

I look for practical ways to preserve decisions, context and working memory so the team can move without interrupting each other for what the system already knows.

A remote team should not have to exchange emails every time someone needs to know something.

If the system knows it, anyone with the right access should be able to ask — and get the current answer, with its source and timestamp.

One person accessing connected organisational knowledge

If one part of the system knows it, the team can know it.

In a team, shared operational memory means people do not need to interrupt another person to retrieve the latest decision, approved process or campaign status.

Has the client email gone out?

Was the tracker updated?

Is there an approved process for this?

What is the current campaign status?

Shared-memory answer

The client email was sent 18 minutes ago.

The final message was approved, sent to the brand contact and copied into the campaign record.

01Remember locally

02Suggest to team memory

03Approve before publishing

04Ask from any approved AI

05See the evidence

06Correct or revoke

Open BlackBox ↗

What this says about me

I understand the trust obligations around client work.

I know when to use the system that already earns confidence, when to connect tools carefully and when a custom build is actually worth the responsibility.

The right workflow for one client may be the wrong workflow for another.

Before automating, I need to know whose information is involved and what obligations travel with it. That means securing client information, checking which tools are appropriate for that account and respecting any competitive boundaries that change what may touch the work.

Existing tools connected into one useful system

01Tool choice follows the client

If Brand A approves a tool, I do not assume Brand B has approved it too.

02Competitor work stays separate

Where Brand A and Brand B compete, their files, prompts, notes and campaign context should not cross.

03Access remains deliberate

People and systems receive only the client information required to do the job.

04The boundary is documented

The team can see which tools are allowed, what was approved and who owns the decision.

I do not reinvent the wheel for the privilege of saying I made a wheel.

Enterprise sense means asking what the system needs to achieve, which risks the team should own, and which risks a trusted platform can carry better. Sometimes the right answer is a custom product. Sometimes it is one thoughtful surface orchestrating tools that already do the hard part well.

Native first.

If a system already handles identity, permissions, delivery or integrations reliably, I would rather use that foundation than rebuild a weaker version and inherit every security and maintenance problem.

The right tool for the right join.

I live in the tools deeply enough to know the difference between a Zapier SDK problem, a Zapier MCP opportunity, an n8n workflow and a process that deserves a small custom interface.

Adoption is part of the architecture.

A clever build that makes the team learn an entirely new world may be worse than an orchestration layer that meets them inside the stack they already trust.

What this says about me

I don’t automate the SOP. I learn how the work actually happens.

Most automation problems are not really “connect A to B” problems. They are operating problems first. I want to understand the business goal, the daily workflow, the invisible workarounds, the exceptions, the handoffs and the places where judgment enters before I decide what should be automated.

THE PROCESS ON PAPER ≠ THE PROCESS IN PRACTICE

An SOP tells me what is supposed to happen. The people doing the work tell me what actually happens.

So I want both. The documented process gives me the intended sequence. Deep conversations with the people inside it show me the workarounds nobody wrote down, approvals happening in DMs, recurring exceptions, dependencies, duplicate work and the moments where somebody has to use judgment rather than follow a rule.

THE SOP

A → B → C → D The clean version.

≠

THE REAL WORK

briefDM approvalspreadsheetexception“ask Sam”manual checkclient rulehandoff

The version the automation has to survive.

THE EXPENSIVE VERSION OF “IT WORKS”

An automation can complete the workflow perfectly and still be the wrong automation for the team.

Moving work from A → B → C → D is not the same as improving the business. A technically successful workflow can automate the wrong process, preserve unnecessary steps, create a maintenance burden, increase risk, or save minutes in one place while adding friction somewhere more important.

WORKFLOW THINKING Can we automate these steps?

A→B→C→D

SYSTEMS THINKING What should the business get back?

less waitingfewer errorssafer handoffsbetter decisionslower maintenancemore capacity

That difference is where I think about return on AI.

BEFORE I BUILD

I want enough operating context to choose the right intervention, not merely a possible one.

01Business goal

What actually needs to become better, faster, safer or more valuable?

02Daily workflow

How does the work move when real people, real deadlines and real clients are involved?

03Friction + gaps

Where are people waiting, chasing, copying, rebuilding context or compensating for the process?

04Exceptions

Which cases break the happy path, and how often do they happen?

05Judgment points

Where does a human still need context, discretion, approval or accountability?

06Existing stack

What already works well enough that I should connect it rather than replace it?

THE BUILD AS EVIDENCE

Our Place Campaigns came from thinking through the whole job, not from starting with a workflow builder.

I worked from the operating rhythm of a campaign: brief, creators, deliverables, approvals, communications, deadlines, payment readiness and the context connecting all of them. That is why the system has different views for different people rather than forcing everyone into one giant dashboard.

Campaign manager coordinating briefs, creators, approvals and timelines

01One system. Different views.

People see what their job requires, not every piece of information the company owns.

02One campaign email.

Comms, files and notes route by campaign, making context reconstruction far cheaper.

03Built around the existing stack.

The team keeps the tools it trusts. The organising layer makes the work easier to see without becoming the only place the work can survive.

04Setup is not a second project.

The intake creates the room, routing address, milestones and starting views.

Explore the campaign system ↗

What this says about me

I do not confuse “it works” with “it is ready.”

I build repeatable checks around quality, risk and readiness so the final review does not depend on memory, luck or last-minute panic.

“It works” is not the same as “it is ready.”

I built a tool that runs 35 Inspector Modules across everything I build. The point is to make quality repeatable rather than heroic.

Person inspecting a detailed readiness checklist

Context

Snapshot

Architecture

Auth

Permissions

Data

Secrets

Dependencies

Database

Concurrency

Jobs

Webhooks

Payments

Privacy

Logging

Retention

Providers

Backups

Performance

Capacity

Costs

Evidence

Release

Live checks

AI systems

Mobile

Payouts

Moderation

Accessibility

Failure states

Recovery

Security

Handoffs

Launch

Open the Inspector Library ↗

Millicent
Yedwa

Before I build, I want to know what should actually change.

Find the opportunity. Build the system. Make it usable.

Understand how the work actually happens.

Build the right layer for the problem.

Make sure the system can survive real work.

Different jobs.
Plenty of overlap.

9-country programme work

NYT bestselling work

Complex information, made clear

Work built to travel

What my automations can tell you about how I think.

I notice when context keeps being rebuilt by hand.

I understand the trust obligations around client work.

I don’t automate the SOP. I learn how the work actually happens.

I do not confuse “it works” with “it is ready.”

Wall of Automations & Strategy

Our Place Campaigns

BlackBox

Rally

The Inspector Library

12-Month Content & Growth Strategy

Know a team
that needs this?

I notice when context keeps being rebuilt by hand.

A remote team should not have to exchange emails every time someone needs to know something.

If one part of the system knows it, the team can know it.

The client email was sent 18 minutes ago.

I understand the trust obligations around client work.

The right workflow for one client may be the wrong workflow for another.

I do not reinvent the wheel for the privilege of saying I made a wheel.

I don’t automate the SOP. I learn how the work actually happens.

An SOP tells me what is supposed to happen. The people doing the work tell me what actually happens.

An automation can complete the workflow perfectly and still be the wrong automation for the team.

I want enough operating context to choose the right intervention, not merely a possible one.

Our Place Campaigns came from thinking through the whole job, not from starting with a workflow builder.

I do not confuse “it works” with “it is ready.”

“It works” is not the same as “it is ready.”

Before I build, I want to know what should actually change.

Find the opportunity. Build the system. Make it usable.

Understand how the work actually happens.

Build the right layer for the problem.

Make sure the system can survive real work.

Different jobs.Plenty of overlap.

9-country programme work

NYT bestselling work

Complex information, made clear

Work built to travel

What my automations can tell you about how I think.

I notice when context keeps being rebuilt by hand.

I understand the trust obligations around client work.

I don’t automate the SOP. I learn how the work actually happens.

I do not confuse “it works” with “it is ready.”

Wall of Automations & Strategy

Our Place Campaigns

BlackBox

Rally

The Inspector Library

12-Month Content & Growth Strategy

Know a teamthat needs this?

Different jobs.
Plenty of overlap.

Know a team
that needs this?