Key takeaways
- Work without a clear owner is the work most likely to stall.
- The aim is to show where ownership is unclear, before a customer notices.
- Each unowned item is designed to reach a leader with a suggested owner and a date.
- In pilot today with design partners.
The problem
Responsibility blurs at the edges of teams. A customer complaint goes to both the account lead and the delivery lead, and each assumes the other will reply. A new process is agreed in a meeting, but nobody is named to run it. A role changes hands, and some of the old work does not move with it. A shared inbox receives a question that belongs to three teams, and all three read it.
These gaps rarely show up in an org chart. They show up as unanswered emails and items that stay open for weeks. When someone finally asks, the answers are polite and honest: "I thought that was with your team." Nobody failed at their job. The work simply had no home.
Picture a growing company on a Wednesday. A new operations lead joined last month and took over two vendor relationships from a colleague who moved to a new project. The handover document covers the contracts. It does not cover the three open questions those vendors raised in email the week before, or the promise made to one of them on a call. Each of those items now sits with someone who has left the role, and with someone who has never heard of it.
Org charts describe roles. Task tools describe tasks somebody entered. Neither shows the work that fell between them, which is where accountability actually breaks.
What GeniOS is designed to surface
In pilot, GeniOS is designed to give an executive a clear view of ownership, drawn from the work itself in email, calendar, chat and the business tools already in use. Each piece of intelligence is meant to name one situation, what to do, why it matters, one owner and a date.
- Orphaned requests. Requests and issues with no clear owner, or with two people who each think the other owns them.
- Handover gaps. Work left behind after a role change or a handover.
- Long-open items between teams. Long-open items, grouped by the teams they sit between, so a leader can see which boundaries are weakest.
- A suggested owner. A suggested owner and a date for each unresolved item, so a leader can decide in one step.
As with all GeniOS intelligence, a person stays in charge: nothing is sent or changed until someone approves it. The leader answers Delegate, Done, Later or Not relevant. When the unowned work keeps routing to one founder, see Founder Dependency Detection; for work that fails at the moment it is passed between teams, see Cross-Team Handoffs.
A worked example
Example at a generic company. Names, dates and numbers are made up to explain the idea.
At a 50-person consulting firm, a client writes to two partners about a delayed report. Each partner forwards the email to their own team, and both teams wait for the other. Five days pass with no reply to the client. In that time the client sends a short second email asking whether anyone has seen the first.
Here is how it would look in pilot: the managing partner receives one note saying the client's email has no owner, two teams believe the other is replying, and one partner should own the reply today. The note shows both forwards, the client's follow-up and the fact that the report was due last Friday. It suggests the partner whose team wrote the original scope, since that team has answered this client's last four questions.
The managing partner delegates ownership to that partner with a date of today. The partner asks a drafting agent for a reply that explains the delay and gives a new date, edits the new date after checking with the analyst, and approves it. The note would close once the sent reply appears in the client thread.
At the end of the month the managing partner sees a short list: four client requests this month waited more than two days because they were sent to two partners at once. The firm agrees that one partner is named lead on each client, and the pattern stops.
How teams use it day to day
The aim is a light weekly habit for executives and team leads.
- Scan the unowned list
Each week, leaders see the few items with no owner or two owners, sorted by how long they have waited.
- Name one owner
Pick the suggested owner or choose another, and set a date. Delegate the follow-up if needed.
- Check handovers
When a role changes, review the open items the previous person was carrying before they get lost.
- Approve before sending
Replies and messages drafted on the owner's behalf wait for approval.
- Fix the weak boundary
Where the same two teams keep dropping work, agree a simple rule for who owns what next time.
Where it applies
These are application areas where this use case can apply, not a list of current deployments. Our design partner work so far is in manufacturing, with Vaultex.
It applies wherever work crosses team lines: client work in professional services and consulting, accounts shared between sales and delivery in software, patient and case coordination in healthcare, and student and programme matters in education. Executive offices, operations, human resources and administration teams usually own the fix.
- Domains: Executive Office, Operations, Human Resources, Administration
- Industries: Professional Services & Consulting, SaaS & Technology, Healthcare, Education & EdTech
- Roles: Executives
Status
Pilot We are shaping this use case with design partners now, and it is not yet a finished part of the product. If this is a problem you have, talk to us about shaping it with us. Design partners are helping us test how suggested owners should be chosen and shown.