Thriving with AI @Work

Human-AI Collaboration

The craft of working with AI.

I run more agents than I have teammates. A few have names and a seat in Slack; most are nameless routines that run and report. Which is which, what counts as a skill, when a script has earned the right to be called a teammate, and how a person and an agent work the same deal without stepping on each other: nobody has settled this yet, me included. I am writing down what I try and what breaks.

AI has expanded what I can attempt: how deeply I can explore an idea, how much I can build, and how many threads I can move forward at once. It has also made new demands on my judgment and attention.

I brainstorm, ask models to challenge each other, and keep shaping the work through conversation. Knowing what to ask, what to trust, what to change, and when to stop is a learned craft. Some of it can be written down. Some of it has to be earned through practice.

The question underneath

What becomes possible when we get better at working together?

One person with AI. Several agents with a shared task. Colleagues who need to use what comes out of it.

A living field guide. I’m writing down practices I use, experiments I’m refining, and questions that remain open.

The practice

A practice you can return to.

Start with something worth doing and familiar enough to judge. Make a result you can respond to, then let the conversation improve it.

  1. Choose

    Find work worth changing.

    What would become easier or newly possible?

  2. Frame

    Give the work direction.

    What matters, and what would excellent look like?

  3. Make

    Get something to respond to.

    What is the smallest useful result I can inspect?

  4. Refine

    Use judgment to shape it.

    What is wrong, missing, or worth exploring further?

  5. Keep

    Carry the learning forward.

    What should the next attempt inherit?

Return wherever the work needs you. A result can change the question; a correction can become a standard. The conversation is more fluid than the diagram.

In practice

Three places to put it to work.

There’s plenty of information. I need to know what to do with it.

Shape a brief I can act on.

I built agents that could research a prospect, draft questions, prepare an email, and assemble a pitch deck. Then I had to read and check all of it. The preparation grew faster than my capacity to use it.

I’m redesigning that workflow around a short brief with suggested next actions. The question is whether it helps me enter the conversation with a clearer sense of what matters and what I can contribute. I want the recommendation, the evidence behind it, and what remains unknown, with detail available when I need it.

For a first experiment, choose a familiar meeting and a small set of notes. Familiarity gives you a way to judge the result. Check the facts that could change the conversation, use the brief, and notice what you still had to figure out yourself.

What I’d look for: After reading it, can I name a useful next move? After the meeting, what helped and what went unused?

See the brief I’m experimenting with

It looks polished. It still isn’t what I meant.

Teach the difference between plausible and excellent.

There is craft in explaining what is off. Sometimes I can name the correction. Sometimes I need the model to interview me, explore alternatives, or help me articulate a standard I recognize but haven’t written down.

An example gives that conversation something concrete to work with. Compare a useful result with one that missed the point. Explain why the difference matters: the intended reader, the decision, the missing context, or the tone. When a correction keeps recurring, capture it in reusable guidance and examples.

The standard still needs a human owner. An instruction can become stale, and an elegant response can be wrong. I want to improve both the result and my ability to tell whether it deserves to be used.

What I’d look for: Can I explain why the next version is better? Can another person use the guidance without asking me the same questions?

Explore how shared standards become useful

The agents can keep going. My attention has limits.

Direct several streams without losing the thread.

I can now make significant progress on several hard problems concurrently. That is exhilarating, and it changes the job. I still have to remember what each stream is doing, which decision is waiting on me, and how the pieces fit together.

Separate work where the dependencies allow it. One agent might explore alternatives while another challenges the assumptions. Give each a clear question, relevant context, and a result you can review. If one task needs a decision from another, that dependency belongs in the plan.

Leave room to bring the work back together. Comparing answers, resolving contradictions, and deciding what to use are work. When the result goes to a colleague, make the recommendation, unresolved questions, and next owner clear. A faster handoff only helps if the other person can act on it.

What I’d look for: Can I tell what is moving, what is waiting, and what needs my judgment? Is the review queue growing faster than I can clear it?

Read my note on parallel work and review

Open questions

Questions I’m still working through.

The tools and the work keep changing. I want to stay explicit about what I haven’t figured out yet.

When does more become too much?

More parallel work can mean more waiting for review. I’m learning where another agent creates useful capacity and where it creates another demand on attention.

What should become a shared standard?

A recurring correction may deserve documentation. It may also be a temporary workaround or a convention worth challenging. How do we keep the useful learning without freezing the practice?

How does expertise grow when the starting tasks change?

If AI makes the first draft, people still need opportunities to reason, make decisions, and learn from consequences. Access to tools and a path to expertise need to grow together.

The other frontiers

From personal practice to shared work.

Individual fluency creates possibilities. Organizations still have to make room for them, and the work has to reach someone who can use it.

Join the exploration

Thriving with AI newsletter

A roughly weekly newsletter where I share what I'm learning and building at the frontier of working with AI @Work and @Home.

Join now for early access to what launches in October and November.

Free, with a 100% money-back guarantee within 90 days.