ARCAS Systems
Chapter 2

The Seven Wastes

The reality

A founder runs a 28 person facilities management business in Abu Dhabi. AED 6.2M (USD 1.7M) last year. Margins have been shrinking for three quarters and the founder cannot find a clean explanation. Pricing went up 8 percent in March. Two clients left, the senior team has been working harder than they were a year ago, and the numbers are tighter every month. When the operations manager walked the founder through one week of work hour by hour, the picture changed. Technicians averaged 2.3 visits per job because the first visit rarely had the right parts. Two other patterns emerged underneath: the office coordinator spending 90 minutes a day chasing signatures on WhatsApp, and proposals taking 11 days to go out because they sat in a folder waiting for the founder to review them. The waste did not show on the P&L as a line item. It showed as a tired team, late renewals, and a margin curve heading the wrong way.

Read this if

  • The team is busy but the numbers are tighter every quarter
  • The same kind of mistake keeps recurring at the same point in the work and the team has stopped reporting it
  • Margins have shrunk despite full delivery teams and full pipelines
  • A simple deliverable goes back and forth three or four times before the client accepts it
  • Approvals stall in the founder's calendar because the team does not have the authority to act
  • Information about a single client lives in three apps and a phone, none of them definitive

What dysfunction costs

The seven wastes are the named patterns the team has stopped seeing. They are also the cheapest margin to recover.

Margin cost. Every recurring waste leaks cash that does not show as a line item on the P&L. A second site visit costs the labour, the vehicle, and the client's irritation. The 90 minute daily approval chase is a senior salary leaking through a manager's phone. An 11 day proposal cycle is half the deals lost to a faster competitor.

Velocity cost. Work that should take three days takes ten. The team feels busy because they are, but the business runs harder for the same revenue and the founder cannot find a single problem to fix. The seven wastes are seven small leaks compounded.

Quality cost. Rework and over-processing both produce the same outcome. The team gets to the deliverable, but the work feels heavy and the client cannot tell why their experience varied from the last project. Variation kills referrals more than poor quality does, because a client who knows what to expect can cope. A client who never knows cannot recommend you with confidence.

Team cost. Smart people stay where they can do real work. They leave when the day is mostly tool-switching, waiting, and re-typing the same data into a different system. The team that quietly resigns first is the one most able to leave for somewhere with cleaner systems. Single-point dependence is covered in Depth Before Width.

What success looks like

When waste is named and managed:

  • A new hire can describe each of the seven categories and point to where each one appears in the work
  • Approval thresholds let the team move without the founder's calendar in the way
  • The most common deliverable has a brief template that catches 80 percent of the rejections before they happen
  • Information lives where it is created and flows from there, without being retyped across three apps
  • A weekly 15 minute meeting clears the backlog of stalled work, and stalled work older than two weeks gets a decision
  • The team estimates the cost of the top three wastes in dirhams and uses the number when prioritising what to fix next

The framework

Naming the wastes is the first step. Removing them takes four moves the team can run as a discipline.

Layer 1: Name what is already happening

Until the team has language for the patterns, the patterns stay invisible. The seven categories (waiting, overproduction, rework, motion, transportation, over-processing, inventory) give the team words. A technician who can say "that is a transportation waste" makes the cause visible, where "I do not know, that is just how we do it" hides it. The visibility move is the same one Process Mapping builds, applied to a different question.

The behaviour to adopt this week: walk through the seven categories with one senior team member and write down one specific recent example for each. Skip categories where no example comes to mind.

Layer 2: Cost the top three

Naming alone changes nothing. Costing the top three sorts what to fix first. Hours per week of the people involved, multiplied by the loaded hourly cost, gives a number the team can argue with. Most service businesses find AED 5,000 to AED 15,000 (USD 1,360 to USD 4,085) per week of waste on a first pass. That is AED 250,000 to AED 750,000 (USD 68,000 to USD 204,000) a year leaving the business in friction.

The behaviour to adopt this week: take the top three wastes from Layer 1. Estimate occurrences per week, hours each, and cost. Write the annual figure on a single line.

Layer 3: One fix, one owner, one review

Resist the urge to attack all seven at once. The founder who designs five fixes scatters the team's attention and delivers none. The founder who designs one fix, names one owner, and sets a 14 day review lands the change.

The behaviour to adopt this week: pick the most expensive waste. Design one rule, one threshold, or one removed step. Name the owner. Schedule the review.

Layer 4: Make the discipline weekly

Waste comes back. New tools, clients, and hires all reintroduce friction the team had eliminated. A 15 minute weekly review of stalled work and the top waste of the moment keeps the discipline alive without becoming a process tax.

The behaviour to adopt this week: schedule a 15 minute weekly waste review for the next eight weeks. The first review is to check the fix from Layer 3 is sticking.

A founder you might recognise

A founder runs a 22 person creative agency in Dubai. The team produces around 180 deliverables a year for clients across hospitality and retail: campaigns, brand systems, social media kits, and the occasional pitch deck. The team is talented. The work is unevenly profitable.

In the second quarter of 2026, the founder ran a waste audit for the first time. The findings were uncomfortable. The team produced three full campaign concepts when the brief asked for one. The brief itself was often a 40 minute call with no written summary, so the next stage started against three slightly different versions of what was being asked. Junior designers were running their own client conversations and extending scope without flagging it to keep the client happy. Unbilled hours had grown to roughly 22 percent of total team hours.

The fix was a one-page brief template, signed off by the client before any concept work started. Anything beyond the briefed scope became a separate conversation with a separate price. Within six weeks, unbilled hours dropped from 22 percent to 15 percent. The team's confidence rose because conversations about scope happened on paper before the work began. The same template now sits in the team's shared drive as the artifact a new designer learns the discipline from on day one. Turning a fix into a re-readable artifact is the move covered in Standard Operating Procedures.

Working through it

  1. Walk the seven categories with one senior team member. Sixty minutes. One specific recent example for each waste, or skip the category if no example comes to mind. The output is a list of 4 to 6 active wastes in your business.

  2. Cost the top three. Estimate occurrences per week, hours per occurrence, and the loaded hourly cost of the people involved. Multiply. The annual figure is the number that decides priority.

  3. Pick the most expensive waste. Design one fix. A rule, a threshold, a template, or a removed step. The fix should land in less than two weeks. Name the single owner who will run it.

  4. Run the fix for 14 days. Then check. Same metric as before, after the fix has had time to bite. Lock the fix in if the number moves. Redesign with the team present if it does not.

  5. Schedule a weekly 15 minute waste review for the next eight weeks. The first review is to check the Layer 3 fix is sticking. Subsequent reviews surface the next waste to attack. Eight weeks turns the discipline into muscle memory.

The deeper working session, with the seven wastes defined, the audit table, and the costing exercise, lives in The Seven Wastes: Core Work.

Common mistakes

  • Trying to fix all seven at once. The team scatters and finishes nothing. Pick the costliest, close it, then move to the next.
  • Blaming people for what the process produces. If three different people make the same mistake, the process is broken. The people are running it as designed.
  • Adding tools to fix process problems. A new project management system does not help if the problem is that nobody writes a brief before starting work. The tool amplifies whatever discipline already exists.
  • Skipping the cost step. A waste that has not been costed in dirhams will not be prioritised. The team will keep working around it for another year.
  • Treating the audit as a one-time event. Waste comes back when new tools, clients, and hires arrive. The weekly 15 minute review is what keeps it from accumulating.

Self-assessment

Y or N for each.

  1. Has the team named at least three of the seven wastes that appear in your work, with a specific recent example of each?
  2. Have you costed the top three wastes in dirhams per week and dirhams per year?
  3. Is there a rule, threshold, or template in place for the most expensive waste?
  4. Does an owner have responsibility for the fix and a date to review whether it is working?
  5. Is there a weekly 15 minute meeting where stalled work gets a decision (finish, send, or kill)?
  6. Has at least one waste reduction been measured with a before number, a fix, and an after number?
  7. Can a senior team member describe the seven categories and point to where each one lives in the business?

Five or more "yes" answers means the team has built the discipline. Three or four is the band where the founder sees the leak but has not built the discipline yet. Two or fewer is where AED 250,000 to AED 750,000 (USD 68,000 to USD 204,000) a year is leaving the business through friction the team has stopped seeing.

Reading page 1

The Seven Wastes: Core Work

Working page for The Seven Wastes.