Work gets stuck between people
A request moves between inboxes, spreadsheets and conversations. It becomes hard to tell who owns the next step.
Explore handoffs →Practical process improvement
For owners and operations leads at small B2B service businesses
Explore practical examples and guidance to help you examine everyday work, spot unclear handoffs, and consider simpler ways forward.

Does any of this sound familiar?
Keeping work moving often means filling gaps between people, information, and tools. That effort can be easy to overlook.
Perhaps a request stalled between people, information had to be entered twice, or checking progress took several messages.
These are starting points for exploration:
A request moves between inboxes, spreadsheets and conversations. It becomes hard to tell who owns the next step.
Explore handoffs →Someone copies details from one tool to another, then checks whether both versions match.
Explore repeated entry →A simple question about progress turns into several messages and a search across tools.
Explore visibility →Your problem may be different. You’re welcome to share something we haven’t described here.
How we work
When work gets stuck, adding another tool isn’t always the answer. Understanding what people are already doing—and what gets in their way—is a useful place to start.
Faber Systems draws on experience in IT operations, systems thinking, and process improvement to understand how people, information, and tools work together.
We use three principles to explore practical improvements:

Examine a real example: the intended outcome, people involved, information needed, and points where work breaks down.
Consider clearer ownership, fewer unnecessary steps, and better use of existing tools.
Check whether a proposed improvement produces the intended result.
This approach guides the improvements we’re exploring. Today, you can read our practical guidance or share an experience to inform what we develop next.
A practical place to start
Our client-onboarding guide includes a simple worksheet for examining how requests, documents, and information move between people.
Use it to identify a handoff worth looking at more closely and consider where simplification could help.
Read the client-onboarding guide →
| Question | What to record |
|---|---|
| What starts this step? | The event or information that makes work ready. |
| Who owns the next action? | A role responsible for moving it forward, with a backup if needed. |
| What information is needed? | Required details, their source and where they belong. |
| Where does work wait? | A missing answer, approval, unavailable person or unclear responsibility. |
| What gets repeated? | Re-entry, repeated requests, checking and correcting. |
| What makes it complete? | A clear condition the next person can check. |
Your experience matters
You don’t need a polished explanation or a proposed solution. Start with something that happened, in your own words.
Tell us what you were trying to accomplish, what got in the way, what you tried, and what happened afterward.
Examples outside the topics above—and critical feedback—help us understand which problems deserve further investigation.
The written form opens on Microsoft’s website. You can share an experience without providing contact details.
We review responses to understand the problem, its context, and questions that need further investigation. Submission confirmation means your response was received, not that it has already been reviewed.
If you do, provide an email address and we may follow up where appropriate. A reply or meeting isn’t guaranteed, and sharing does not create a project commitment.
If you would prefer to discuss a problem, you can express interest in a conversation →.
Participation is voluntary. Please leave out passwords, client names, confidential records, and sensitive personal information.