Seraf’s COO advisor: operations, processes and project tracking

In a large company, the chief operating officer turns leadership’s priorities into concrete deliveries. In a business with a few employees, that role is often filled by the owner, somewhere between a quote and an invoice. The COO advisor brings that perspective without taking anyone’s place: its mission covers delivery, capacity, processes, dependencies and deadlines.

It aims for three outcomes. First, a reliable delivery flow: the work you promised moves forward in an order that makes sense. Next, visible blockers: a stalled task doesn’t stay hidden in a conversation. Finally, commitments that take real capacity into account: you don’t promise three installations in the same week when only one crew can do them.

To get there, it watches for four signals:

• a blocked delivery, for example an order that has been waiting for approval for several days;
• a capacity shortfall, when the planned work exceeds the hours available;
• a late dependency, such as a supplier, a set of drawings or client information that isn’t arriving;
• a failing process, meaning the same mistake coming back from one project to the next.

The COO belongs to the Council’s first ring, along with the CEO advisor, the Chief of staff, the CRO, the CFO, the CTO and the Customer director. The seats in this ring review the situation every morning, including on days when nothing important comes up. On those days, the seat stays quiet rather than adding noise to your brief.

You don’t talk to the COO advisor directly. Seraf remains your only point of contact. When a question touches your operations, it can consult the Council, then it presents a single recommendation, the reason behind it and a next step. You don’t see a debate between advisors: you see a clear proposal, and the decision is yours. In the morning brief, its recommendations come back to you with the choice to accept, edit, postpone or decline.

The Council also prepares items for your morning brief. The app shows the seat concerned there, for example the COO advisor, along with its mission, so you know which point of view a proposal comes from. Some proposals then offer to launch or prepare the work with Seraf.

Its decision rights are deliberately narrow. It can:

• recommend a delivery sequence;
• flag a capacity risk;
• ask for a dependency to be resolved by the person responsible.

Its reserved actions are just as clear: no staffing change, no production deployment, no external commitment. It doesn’t reassign an employee, doesn’t change a work schedule and doesn’t confirm a delivery date to a client. If it judges that a commitment needs to change, it flags it; the decision goes back to the human owner.

The seat doesn’t work alone. It relies on the Chief of staff, who follows coordination and prepares decisions, on the CTO advisor for anything involving your tools and website, and on the Delivery and project operations function, which follows the work under way and its deadlines. The guide to the CTO advisor and access security shows the other side of this pairing. When a capacity shortfall comes from the team itself, the HR advisor brings its own perspective on onboarding, roles and workload.

A recommendation stays a recommendation. If Seraf then prepares a message to a supplier or a project update, any sensitive action, such as sending, deleting or changing access, requires your explicit confirmation before it goes ahead.

An advisor only sees what your tools show it. Before you expect good recommendations about your operations, describe how work really flows. The BDC presents process mapping (new tab) as a diagram of the sequence of activities that spells out who does what, when and how. It suggests following a process from end to end, for example from order intake through to invoicing, and starting simply, with sticky notes on a wall. Above all, it recommends involving the people who carry out these activities every day: they are the ones who know where the work gets stuck.

This map often reveals a bottleneck. According to the BDC, a bottleneck occurs wherever there isn’t enough capacity or capability to perform the tasks (new tab). To find it, watch where work piles up, then measure how often and how long work stops. The BDC advises pinning down the true cause before hiring or buying equipment, and sharing the data with your staff so they can propose solutions. That is the discipline you would expect from a good operations advisor: understand before recommending.

In Serafex, several spaces give you this visibility, depending on your account:

• the Pipeline brings together a personal and team task board, as well as a Projects view;
• project notes let you hand a task to Seraf while spelling out the conditions for success;
• missions followed through end to end carry a goal, a target and success criteria, which lets you check that a piece of work is truly finished;
• the Calendar and Documents keep meetings, absences and file versions in one place.

The Procedures module, like Inventory and Manufacturing routings, is still in development. For now, your procedures can live in your documents and project notes. The guide to organizing your business’s work with Seraf offers a method for linking each request to an owner and a next action.

The following table helps turn a vague operational unease into information you can act on. It doesn’t reproduce a screen from the app: it is a preparation grid to fill in with your team.

Before asking Seraf for advice on your operations, check these points:

• every active project has a named owner and a next action;
• deadlines promised to clients are entered in a project, not just in an email;
• planned absences are in the calendar;
• external dependencies have an expected date;
• you know which criterion will tell you a project is finished.

An incomplete grid shows where visibility is lacking, and that gap is often the first problem to fix.

Here is a situation invented to illustrate the role; it doesn’t describe any Serafex client. An eight-person cabinetmaking shop has to deliver two kitchens in the same week. The lead finisher is on vacation from Wednesday to Friday, and the hardware supplier announces a four-day delay on the hinges for one of the two projects.

On Monday morning, the owner’s brief contains an item presented under the COO advisor seat. Seraf sums up the situation: the two deliveries can’t both fit within the finishing capacity available. Its recommendation: finish first the kitchen whose hardware is already on hand, and warn the second client today about a possible delay. The reason: the supplier’s delay already puts the second date at risk, and the finisher can’t complete both projects before leaving. The proposed next step: prepare a draft message to the second client and update the project in the Pipeline.

The owner edits the proposal. She prefers to call the client herself, accepts the project update and asks Seraf to prepare a follow-up to the supplier. The follow-up stays a draft until she confirms sending it. Nothing changed in the team’s schedules, and no new date was promised without her.

On Friday, the finished project is closed with its record: delivery date, photos and an invoice to prepare. The lesson is noted: order the hardware before scheduling the finishing. If the same delay comes back, the “failing process” signal will rest on facts.

The advisor made a conflict between capacity and commitments visible, then suggested an order. Talking to the client, changing a schedule or promising a date stayed in your hands.

Let’s talk about your operations and what the Council can prepare for you.