The Operator Under Pressure
You've been running Cowork for 60 days. Marcus wants a board-ready analysis by Monday — and the work pushes against every shortcut you've built so far.
Five modules in, you've picked the right Cowork role-pack, run the first-60-minutes setup, internalized the proactive-safety habits, learned the agent-verification rituals, and walked the eight common mistakes. This capstone is the Friday afternoon where the habits get tested. It's 3 p.m. on Friday. Marcus needs a board-ready analysis by Monday morning. The work pulls from three sources, includes complaint records with Sarah's PII, and lands on a draft analysis with three load-bearing claims — one of which has a number that's exactly round. You have a scheduled routine that already fires weekly for a different report. You have a connector lineup you've been deliberate about. You have the pressure of a date. Four nodes, then a fifth that asks you to name what you almost did wrong. Each node is a procedural-rule test: does the rule hold under time pressure, or does the pressure win? Pick the path you can defend.
It's 3:14 p.m. on Friday. Marcus stops by your desk: "Board meeting Monday at 9. I need an analysis pulling from the warehouse, the support ticket database, and Salesforce. Can you have it for me Sunday night?" The warehouse and the ticket database are connected to your Cowork instance — you set them up the second week of your role-pack rollout. Salesforce is not. Your cowork-by-role starter pack didn't include it; you've deliberately kept your connector lineup short for sixty days. Devon, the Director of IT, is at his desk down the hall and is the person who'd add the Salesforce connector if you ask.