It can reconcile records across tabs and systems, identify where a workflow is stuck, prepare a handoff, and run repeatable checks on a schedule. It should not resolve a policy exception, change a financial record, or make a customer commitment without the operator who owns that decision.
01
The exception list is often the real operating dashboard.
A headline metric cannot show which order, customer, supplier, employee, or record actually needs attention. Strawberry can compare the expected state with the observed state and produce a finite queue of exceptions with the source evidence beside each one.
02
Handovers fail when the reasoning leaves with the person.
A good handoff includes more than status.
It records what happened, why it matters, what was already attempted, what is blocked, the next deadline, and the person who can unblock it.
03
Process improvement begins with the path work actually takes.
Documented process and real process often diverge.
Use the browser trail, tickets, forms, and timestamps to map the actual handoffs, repeat loops, delays, and manual judgment points before proposing automation.
04
Recurring operations work should report what changed.
Routines are useful when they monitor a defined system and return a delimited result.
Save a clear check as a skill, schedule it, and ask it to report new exceptions, cleared exceptions, and items that cannot be assessed rather than sending a generic “all clear.”