How to Increase Productivity with AI

Alex Bordei, co-founder of igodemy, speaking at an AI training session.

TL;DR — The companies pulling ahead in 2026 are not the ones with the most AI tools. They are the ones whose employees have rebuilt their workflows around AI. This guide shows you exactly how — by team, by task, with prompts you can paste tomorrow morning.


Most employees don’t have a time problem. They have a workflow problem.

In every audit I run inside large organisations, I see the same pattern. People are busy. Calendars are full. Inboxes are unread. And yet, when we measure where the hours actually go, 40 to 60 percent of the work that fills the week is mechanical — reformatting, summarising, retrieving, drafting, chasing, status-updating, meeting-recapping, slide-tweaking.

That is the work AI is best at. Not “creative replacement”. Not “agents will run your business by Friday”. Just the silent, draining tax that no one wrote in their job description but everyone pays.

The performers who are pulling ahead this year are not faster typists. They are not working longer hours. They have done something simpler and more radical: they have stopped doing the mechanical work themselves. They have moved it to an AI layer that sits between them and the work — and they now spend their human time on judgement, taste, decisions, and people.

This article is the practical playbook for joining them.


What AI actually changes about productivity

For two decades, “productivity software” meant faster typing of the same artefacts. A faster word processor. A slicker spreadsheet. A nicer task manager. The artefact stayed; you just produced it with less friction.

Modern AI is a different kind of tool. It does not make you faster at producing the artefact — it removes the need for many of the artefacts in the first place. You do not write the meeting recap; the meeting recap writes itself. You do not draft the first version of the proposal; the draft is waiting for you when you open the file. You do not search for the contract clause; you ask a question and receive an answer with the source.

That difference matters. The companies that treat AI as a faster typewriter see modest gains — maybe 10–15 percent. The companies that treat AI as a co-worker that handles the mechanical layer of every workflow routinely report 30–50 percent gains in throughput per person, sometimes much more.

The shift is not from human to AI. It is from human-doing-mechanical-work to human-doing-judgement-work, with AI handling everything in between.


The four leverage axes: where AI compounds

Useful AI productivity work always sits on at least one of these four axes. If you can name which axis you are pulling, you will pick the right tool and the right prompt without thinking.

1. Time leverage

The same output, faster. Drafting an email in 30 seconds instead of 10 minutes. Summarising a 90-minute meeting in 20 seconds instead of an hour. This is the most obvious axis and the easiest to measure.

2. Decision leverage

Better quality of judgement, at the moment of judgement. Before you commit a number to the forecast, you ask the model to challenge the assumptions. Before you send the message, you ask it to find the three weakest points. AI does not make the decision — it makes you a sharper decision-maker.

3. Cognitive load leverage

The work gets done with less mental tax. You stop holding seven things in your head because the model is holding them for you. You stop dreading the inbox triage because it is already triaged when you sit down. The savings here are invisible in a spreadsheet but very visible on a Friday afternoon.

4. Context-switch leverage

You stay in deep work longer. Instead of jumping into five tabs to gather sources, you ask one question and get one answer. Instead of opening Slack to ask a colleague for the status, you ask the AI that already knows. Every context switch costs about 23 minutes of focus. AI productivity, done well, removes most of them.

The strongest workflows pull two or three axes at once. That is when the compounding starts.


AI productivity by team

This is the operational part of the article. For each team, you will find: where AI moves the needle most, an example workflow before vs after, and a prompt you can copy.

Marketing teams

Where AI compounds: research, drafting, repurposing, briefing, performance analysis.

Before AI — A B2B content marketer writes one cornerstone article per month. Most of the time goes into research (three days), then drafting (two days), then internal review cycles (one week).

With AI — The same marketer drafts in a half-day, with a research synthesis the model produced overnight from 40+ sources, then spends the saved time on distribution, interviews with customers, and measurement — the parts of marketing that actually move pipeline.

Example prompt for content briefing:

You are a senior B2B content strategist for [company / category].
Build a content brief for an article on [topic], targeting [persona].

Cover:
- the 3 questions this persona is searching for right now,
- the 5 keywords that should anchor the piece (mix of head + long-tail),
- the angle that will differentiate us from the top 5 search results,
- a recommended outline with H2/H3 hierarchy,
- the 2–3 sources I should interview internally before writing.

Measurable shift: Top-performing marketing teams have moved from 1–2 cornerstone assets per month to 6–8, with the same headcount, and stronger pipeline contribution per asset.

Sales teams

Where AI compounds: prospect research, call prep, follow-up drafting, CRM hygiene, deal coaching.

Before AI — An account executive spends 60 percent of the week on admin: writing emails, updating CRM, prepping calls, building decks. Selling time is maybe 40 percent.

With AI — Selling time goes to 60–70 percent. The model writes the follow-up the moment the call ends, the CRM updates itself from the transcript, and the next-call brief is in the AE’s inbox before their morning coffee.

Example prompt for pre-call brief:

You are an SDR analyst. Build a 10-bullet pre-call brief for a meeting with
[name] at [company]. Pull from:
- their LinkedIn,
- the company's last 4 press releases / blog posts,
- the latest 10-K filing if public,
- their job description as inferred from their title.

Output:
1. What they likely care about right now.
2. The single best opening question.
3. Two risks I should pre-handle.
4. One specific reference customer to mention.

Measurable shift: Sales orgs running AI well are reporting 25–40 percent more meetings per AE per week, and shorter cycles because pre-call prep is no longer the bottleneck.

Operations teams

Where AI compounds: standardisation, documentation, exception handling, vendor management, internal reporting.

Operations is the team with the highest ratio of mechanical work to total work. It is also the team where AI gains are most under-claimed, because nothing about ops is glamorous.

Workflow example — vendor invoice triage. A finance ops team used to spend two days a month routing invoices to the right cost centre. Now an AI workflow reads each invoice PDF, extracts the line items, matches to the PO, classifies the cost centre, and only escalates the genuinely ambiguous cases — about 8 percent of the volume.

Example prompt for SOP generation:

You are an operations excellence partner. I am going to describe a manual
process. Convert it into a clear SOP with:
- objective,
- inputs,
- step-by-step instructions (numbered),
- decision points (with criteria),
- expected outputs,
- failure modes and how to detect them,
- the parts that should be automated next.

Process: [paste here]

Managers and executives

Where AI compounds: information synthesis, decision support, communication clarity, talent development.

A senior leader’s job is mostly about three things: deciding, communicating, and developing people. AI helps with all three, and most leaders are still using it for none of them.

Decision support pattern: Before any meaningful decision, you paste the decision memo into the model and prompt it to argue the opposite of your current preference. You read the argument. You strengthen the parts of yours that survive. You change your mind on the parts that do not. This is the closest thing to a virtual board you can run, on demand.

Communication clarity pattern: Before any message goes to more than 10 people, you ask the model to identify the three sentences that will be misread, and rewrite them. The internal politics of large companies are mostly about avoidable misreads. Removing them is high leverage.

Example prompt for a decision pressure-test:

You are a senior advisor with the candour of a former CEO.
Below is a decision I am about to make. Your job is to argue the strongest
case AGAINST it. Do not soften the argument. Use specifics from the memo.

Decision memo: [paste here]

Individual contributors

Where AI compounds: deep work, learning curve, communication, repetitive tasks.

The single highest-impact habit for any IC is to keep a chat open during the entire workday and treat it as the thinking partner you do not need to schedule with. Not for finished work. For half-formed thoughts, for stuck moments, for “is there a name for what I am trying to do?” type questions.

Workflow: End every day with a 5-minute review. Ask the model: “Here is what I worked on today: [paste]. What would a more experienced version of me have prioritised differently?” You will end your first month a meaningful step ahead of where you would have been otherwise.

Customer support

Where AI compounds: knowledge retrieval, response drafting, sentiment analysis, escalation routing.

The first wave of “AI in support” was bad chatbots. The current wave is far more interesting: the model sits between the agent and the customer, drafting the response, citing the right help article, flagging sentiment, and producing the summary for the CRM.

Measurable shift: First-response time down 40–70 percent. Agent satisfaction up — because the boring half of the job is gone and they spend time on the cases that actually require empathy and judgement.

Research and strategy teams

Where AI compounds: literature review, synthesis, qualitative coding, hypothesis generation, executive reporting.

A strategy analyst can now do in two days what used to take a team a fortnight: scan a market, code 50 interviews, build segment archetypes, and produce a board-ready brief. The bottleneck moves from collecting data to knowing which question to ask next. That is exactly where you want your most expensive humans spending time.


Frameworks the highest performers actually use

The “Second Brain” pattern

Treat the AI as a memory layer for everything you read, listen to, and decide. Paste meeting transcripts, articles, voice notes, and decisions. Tag them. Now the model can answer questions across everything you have ever cared about, not just what is in the current chat. This single habit changes the texture of knowledge work more than any prompt ever will.

The “Thinking Partner” pattern

Do not ask the model to give you answers. Ask it to make you think better. Prompts that move you here: “What is the question I am not asking?” “Where am I being lazy in this analysis?” “What is the strongest counter-argument?”

The “Workflow Stacking” pattern

A single AI step is useful. Stacked AI steps are leverage. Transcript → summary → action items → draft follow-up email → calendar holds for next steps → CRM update. Each step is two minutes. The whole pipeline runs in the time it takes to walk to the kitchen.

The “Deep Work Cocoon” pattern

Pre-load the model with all the context for a deep-work block — the spec, the customer research, the constraints, the previous attempts — then close every other tab. The model becomes your sole conversational interface for the next two hours. Notifications stay outside. Output rises sharply.

The “Critical Review” pattern

Never ship important AI-assisted output without one explicit human pass focused only on what the model cannot know: your relationships, your judgement, your taste, your stakes. This is the part of your job that should never be delegated.


Advanced patterns most articles miss

  • Prompt engineering for productivity is not about clever tricks. It is about being a better briefer. The same skills that make you good at delegating to a sharp junior teammate make you good at prompting.
  • The best operators run multiple models. They use Claude for long-form reasoning and writing, ChatGPT for tools and structured tasks, Gemini for retrieval-grounded answers, and Perplexity for “what is the latest” questions. Different models, different strengths — and the choice is part of the craft.
  • Memory is the most under-used feature. Personal memory in ChatGPT, Claude, and Gemini means the model remembers your style, your team, your projects. The compounding starts the moment you start curating that memory deliberately.
  • The single biggest unlock is voice. Talking to the model while walking is faster than typing in front of a screen and produces remarkably different ideas. Try this once and you will keep doing it.
  • AI is a humility instrument. It will routinely point out that you skipped a step, missed a stakeholder, or used a vague word. The leaders who let themselves be challenged in private by an AI are the ones who stop being challenged in public by their peers.

What AI does not fix

A short list, because no honest piece on AI productivity is complete without it.

  • AI does not fix a broken process — it accelerates it. Automate a bad workflow and you produce bad output faster. Fix the workflow first.
  • AI does not replace judgement. Especially in regulated industries, escalations, edge cases, and human conflict, the human stays in the loop.
  • AI does not fix culture. If a team does not trust each other, AI will not help them collaborate. It will just give them faster ways to argue.
  • AI does not remove the need for deep expertise. The people who get the most out of AI are the people who already know enough to spot when the model is wrong.
  • AI does not protect you from hallucinations and confident-sounding errors. Verify anything load-bearing.

Your 30-day implementation plan

If you are reading this and you want to feel the difference inside a month, here is the path.

Week 1 — Pick one workflow. Choose the single task you do most often that you also find most tedious. For most people: weekly status updates, meeting recaps, or inbox triage. Do not pick something glamorous. Pick something mechanical.

Week 2 — Build the prompt and use it daily. Write a clean, reusable prompt for that workflow. Keep it in a notes app. Use it every single day. Refine it three times.

Week 3 — Stack one more workflow. Now add a second one. Ideally connected to the first — for example: meeting recap → action items → follow-up draft. The compounding starts here.

Week 4 — Share what works. Tell your team. Show them the prompt. The single highest-leverage thing a senior person can do this quarter is make their best prompts shared assets. This is how AI productivity stops being individual and becomes organisational.

By the end of those 30 days you will have a clear picture of where you, specifically, are losing hours — and a working AI layer that gives you most of them back.


FAQ

What does “AI productivity” actually mean?

It means using AI tools to do the same work in less time, or higher-quality work in the same time. In practice, it is the use of large language models, agents, and AI-augmented software to remove mechanical steps from knowledge work — drafting, summarising, retrieving, scheduling, reporting — so humans focus on judgement and relationships.

Which AI tool should I start with?

For most knowledge workers in 2026: Claude for long-form reasoning and writing, ChatGPT for general tasks and tool integrations, Perplexity for current research, Gemini for Google-ecosystem work. Pick one as your default, master it, then add a second.

How much time can AI realistically save me each week?

Empirically, motivated individual contributors recover 5–10 hours per week within their first 60 days of deliberate use. Managers and senior leaders recover more, because the proportion of their work that is synthesis-heavy is higher.

Is AI productivity safe to use with confidential data?

Use enterprise versions (Claude for Work, ChatGPT Business, Gemini for Workspace) that come with data-protection terms. Never paste regulated personal data, secrets, or client-confidential information into consumer tools without checking your company’s policy.

Will AI replace my job?

AI will replace specific tasks, not specific people. The people whose jobs change most are the ones who treat AI as a threat rather than a leverage point. The most resilient career move you can make right now is to become the person on the team who is clearly best at using AI for the work that already exists.

How do I prompt better?

Brief AI the way you would brief a sharp junior teammate. Tell it the role, the context, the audience, the constraint, and what good output looks like. Show one example if you can. That is 80 percent of prompt engineering.

What is the difference between an AI tool and an AI agent?

A tool answers a question; an agent takes an action. Tools save you minutes. Agents save you whole workflows. Most teams should be fluent with tools first, then introduce agents for two or three repeatable, well-bounded processes.


The future of AI-native work

The most striking shift inside the companies I work with this year is not technological. It is cultural. The conversation has moved from “should we let people use AI?” to “why is this person not using AI yet?” The norm has flipped.

The companies that will look obviously ahead in twelve months are doing three quiet things now:

  1. They have named the workflows that should be AI-first, and the ones that should stay human-first.
  2. They have invested in their people’s craft — better prompting, model literacy, evaluation skills — instead of buying yet another tool.
  3. They are rebuilding the management contract: less time on status updates, more time on coaching, more time on decisions, more time on customers.

AI is not the next productivity app. It is a new substrate underneath every productivity app you already have. The teams that act on that — quietly, methodically, this quarter — are the ones who will look obviously ahead next year.

You do not need a transformation programme to start. You need one workflow, one prompt, and one week.

Start there.


Alex Bordei is co-founder of igodemy, where he leads the technical practice and the corporate AI training program. If you want to bring this thinking into your team, get in touch.

Interested in working together?

We'd love to hear about what you're building.