The short answer.

Act on the AI ideas your people suggest when each idea, written as a piece of work for one role, passes four questions: the work repeats, it starts from records you already keep, one named person checks the result, and someone will own the workflow. An idea that passes joins your AI plan in order, behind the work already there. An idea that fails gets a plain “no for now”, with the question it failed and the date you will look again.

The people doing the work know where the week repeats. Sorting their ideas is part of planning, the first of three steps: plan it, develop the workflows, deploy them. How to choose the first three things to build with AI picks the opening work. The intake on this page handles everything people suggest after that, every month.

Every idea comes through one intake.

Every AI idea, from any person in any team, goes to one place and one person. The place is a short form. The person is whoever owns the AI plan. Ideas that arrive in a hallway, a team meeting or a message go onto the same form, filled in by whoever heard them.

Without one intake, the loudest idea gets built, the quiet good one is forgotten, and people stop suggesting because nothing came back.

Write each idea as a piece of work for a role.

An AI idea becomes something you can decide on once it names the role that does the work, what the work starts from, what it produces and who receives it. “Use AI for customer emails” cannot be sorted. “The wholesale account coordinator writes the weekly order confirmation to each café, from the order system export, and the café owner receives it” can.

Rewrite each idea with the person who suggested it, in one sentence with those four parts. Some ideas split into two or three pieces of work. Some turn out to be a tool or training request and go to the right person instead. How to plan AI by role explains why the role, not the person, is the unit the plan is built on.

Four questions sort every idea.

Ask the same four questions of every idea, once the idea is written as a piece of work for a role.

  1. Does the work repeat?The work happens every day, week or month, the same way each time. Work that changes shape every time stays with a person and their assistant, not in a workflow.
  2. Does it start from records you keep?The inputs come from a system or a file someone already exports: the order system, the accounting system, a spreadsheet. Inputs in inboxes and heads get gathered first.
  3. Does one named person check the result?Someone already reviews the work before it leaves the team. The workflow prepares; that person decides.
  4. Will someone own the workflow?One person, by name, keeps the workflow current and reads its misses. Often the person who suggested the idea is the right owner.

The four questions are gates, not scores. An idea that passes all four is ready. An idea that fails one waits, and the failed question tells you what has to change first.

Two answers: in the plan, or no for now.

Every idea gets one of two answers within a month of arriving. There is no third pile marked “maybe”.

  • In the plan, in order.The piece of work goes under its role in the plan, behind the work already queued for that team. It does not jump the queue because it is new or because a senior person suggested it. Ideas that start from the same records as work already in the plan move up, because the inputs are already gathered.
  • No for now.The answer names the question the idea failed, what would change it, and the month you will look again. “No for now: the café orders still arrive by phone. Once orders come through the order system, we look again in September.”

The person who suggested the idea hears the answer from the plan’s owner, in person or in writing. A plain no with a reason keeps people suggesting. Silence stops them.

An intake form to copy.

Copy these headings onto one page. Fill in one form per idea. Write “Unknown” where nobody knows, with who will find out.

  1. Suggested by, and when.The person’s name and the date.
  2. The idea, in their words.One or two sentences, as they said it.
  3. The piece of work.The role that does it, what it starts from, what it produces, who receives it.
  4. How often.Daily, weekly, monthly, or less.
  5. Where the inputs live.The system or file, and whether someone exports it today.
  6. Who checks the result.One name, or “nobody yet”.
  7. Who would own the workflow.One name, or “nobody yet”.
  8. The answer.In the plan, with its place in the order, or no for now, with the failed question and the month to look again.
  9. Told on.The date the person who suggested it heard the answer.

A bakery sorts a month of ideas.

Take a 50-person regional bakery with two sides: wholesale, which supplies cafés and grocers, and retail, which runs three shops. The operations director owns the AI plan and runs the intake. Wholesale invoicing is already the first workflow in daily use. In one month, five ideas arrived.

Illustrative example.

  • Order confirmations, from the wholesale account coordinator.Written as: the coordinator sends each wholesale customer a weekly order confirmation, from the order system export. It repeats weekly, the export exists, the wholesale manager checks it, and the coordinator will own it. The answer: in the plan, next for wholesale, because it starts from the same export as invoicing.
  • Daily production sheet, from the head baker.Written as: the head baker turns tomorrow’s wholesale orders and shop forecasts into the overnight production sheet. It repeats daily and the head baker checks every sheet, but the shop forecasts live in each shop manager’s head. The answer: no for now. The shop managers start entering forecasts in a shared spreadsheet; the idea is looked at again in two months.
  • Social posts, from a shop assistant.Written as: each shop posts its daily specials. The posts differ every day and nobody checks them. The answer: no for now, as a workflow.
  • Allergen labels, from the retail manager.Written as: the retail manager updates shelf labels when a recipe changes, from the recipe file. It repeats with every recipe change, and the head baker signs off every label. The answer: in the plan for retail, first in its order.
  • “Use AI for hiring”, from a shift supervisor.Split into two pieces of work: drafting seasonal job posts and scheduling interviews. Neither repeats often enough yet. The answer: no for now, looked at again before the holiday season.

Every person heard their answer that week. The order confirmation starts from a free workflow template in the Workflows Directory, adapted to the bakery’s own order export and tested on last month’s orders before any customer sees one.

The plan’s owner runs the intake every month.

The person who owns the AI plan reads every new form once a month and gives every answer. Ideas marked “no for now” come back up in their month. How to run a monthly AI review sets out that meeting; the intake is its first agenda item.

What is different in a company of under 200 people.

In a company of under 200 people, the plan’s owner can answer every idea personally, and every idea deserves that. A large company runs an innovation programme with a committee. You have one owner, one form and one monthly sitting.

  • The suggester often owns the result.The person who knows the work well enough to suggest an idea is usually the right person to own the workflow.
  • A no travels fast.Everyone hears how ideas are answered. A plain no with a reason and a date tells the whole company that suggesting is worth it.

Put every idea in one place and give each its answer. FullyPowered Planner is where the plan lives: you set out your teams, their roles and the work between them, choose what to build first, and your colleagues add their own teams. How organizations plan their use of AI covers the rest of the method.