OPERATIONS
How work moves
through your business
without getting stuck.
Operations is the domain that determines whether work flows smoothly or constantly requires manual coordination to stay moving. When it is tended, the right people do the right things at the right times without anyone having to remember to ask. When it is quiet, the business is burning energy just staying organised.
Domain 04 · Typical State
Waiting
Most active partnerships
30%
Of business time typically lost to coordination overhead
Core workflows documented and in a system
Task management tool configured and in use
No critical work running purely on email
Handoff points defined and owned
At least one repetitive process automated
What this domain is
The manual handoff is the most expensive thing
in most businesses.
Operations is the layer that sits between your people and their best work. When it is tended, work moves from person to person, stage to stage, without friction. When it is not, every project requires constant coordination: who is doing what, where things are, what the next step is, whether it has been done.
The cost is not visible in any line on the income statement. It shows up as hours lost to status updates. As things discovered not done because nobody was explicitly responsible. As the same mistake happening repeatedly because nobody wrote down how to avoid it. As the owner being the integration layer for their own organisation.
Operations is typically a Waiting domain. The infrastructure can be built quickly. But process adoption takes time. Yutie documents, builds, and then monitors adoption in the monthly Shalom Score review until the domain is genuinely Tending.
2.5h
Lost per person per day to coordination
Research by McKinsey found the average knowledge worker spends 28% of their day on email coordination. Operations work reduces this.
3×
Improvement in task completion
Organisations with structured task management complete projects at three times the rate of those that rely on verbal handoffs.
80%
Process failures from people, not tools
Most operational failures are not technology failures. They are process failures: unclear ownership, missing documentation, undefined standards.
What Yutie does here
Every service in this domain,
named and explained.
Every service in the Operations domain is about removing friction from how work moves. Not adding complexity. Removing it. Every intervention is measured by whether it makes things simpler for the people doing the work.
01
Workflow Mapping and Documentation
Before anything is built or automated, Yutie documents how work actually moves through the business: the real process, not the intended one. This produces a map that most businesses have never seen and that becomes the foundation for all Operations work.
Stakeholder interviews with the people doing the work
As-is process documentation for 3 to 5 core workflows
Bottleneck and handoff point identification
Time-on-task estimation per workflow stage
Process map delivered as visual diagram and written document
Gap analysis: where the process breaks down and why
Priority sequence for which workflows to fix first
02
Task Management System Configuration
Yutie selects, configures, and deploys the task management infrastructure appropriate for the business: inside Perfex CRM, or a dedicated tool, based on team size and complexity. The system is configured to match how work actually moves, not how a tool wants it to move.
Tool selection based on team size and workflow type
Project templates for recurring work types
Task assignment and ownership rules
Due date and priority configuration
Checklist templates for multi-step tasks
Notification rules: who gets alerted when
Mobile access configuration for field teams
03
Project Templates for Recurring Work
Every project that a business does more than once should have a template. Yutie builds standardised project structures for the recurring work types so that every new project starts with the right tasks already created.
Core project types identified from workflow map
Task list template per project type
Milestone and deadline structure per template
Sub-task checklists for complex deliverables
Resource allocation fields
Client communication checkpoints built in
Template tested on a real project before finalisation
04
Approval Workflow Design
Undefined approval chains are where projects stall. Yutie maps and formalises who needs to approve what, at what stage, with what turnaround time expected, so nothing waits on an approval that nobody knew was needed.
Approval stage identification per workflow type
Approver assignment per stage
Turnaround time expectation documented
Escalation path when approval is delayed
Notification trigger for pending approvals
Approval audit trail configuration
Out-of-office approval delegation rules
05
Standard Operating Procedures
Recurring tasks done consistently across the organisation need written procedures so they produce consistent results regardless of who does them. Yutie writes and formats SOPs for the most critical operational tasks.
Priority SOP list from workflow map
SOP written in plain language with numbered steps
Screenshots or diagrams for visual clarity
Version numbering and last-updated date
Storage location in shared file system
Review schedule (typically annual)
Training integration: SOPs used in onboarding
06
Tool Integration and Automation
The tools a business uses should pass data to each other automatically. Manual re-entry of the same information into multiple systems is eliminated when Yutie connects the tools that should be talking.
Audit of all tools currently in use
Integration map: which tools should share which data
Zapier or native webhook integration configuration
CRM to task management automation
Form submission to task creation automation
Invoice generation from project completion automation
Integration testing and failure alerting
07
Team Communication Architecture
Not every business needs a new communication tool. But every business needs clarity about which tool is for what purpose, what response time is expected on each channel, and how decisions get documented.
Communication channel audit (email, WhatsApp, calls, Slack)
Channel purpose definition (which channel for what)
Response time expectation by channel
Decision logging process (where decisions are recorded)
Meeting cadence recommendation
Meeting agenda and notes template
Communication protocol documented and shared
08
File and Document Management
Files in inboxes, on personal computers, and in WhatsApp threads are operations that nobody can find. Yutie designs and implements the folder structure, naming convention, and access architecture for the business's documents.
Shared storage platform configuration (Google Drive or equivalent)
Folder hierarchy designed by function and project
File naming convention documented
Access permissions per role
Archive structure for completed projects
Document version control protocol
Migration of critical files from personal to shared storage
09
Bottleneck Resolution
After the workflow mapping, Yutie identifies the specific points where work consistently gets stuck and designs targeted interventions to remove each bottleneck. This is the highest-return Operations work.
Bottleneck root cause analysis
Redesign of the specific workflow stage causing the jam
Responsibility reassignment where needed
Automation opportunity assessment at each bottleneck
Time-to-completion tracking before and after intervention
Three-month follow-up check on resolved bottlenecks
10
Accountability Infrastructure
Making ownership visible without micromanaging is the difference between a team that self-organises and one that needs constant direction. Yutie builds the infrastructure that makes accountability the default.
Task ownership rules: every task has one owner
Due date culture: every task has a due date
Status visibility: team lead sees all task status without asking
Overdue task alert configuration
Weekly team summary report automation
Monthly completion rate reporting for Shalom Score
11
Onboarding Process for New Team Members
Every new team member who joins without a structured onboarding process costs the business weeks of productivity. Yutie designs and documents the onboarding sequence for each role.
Role-specific onboarding checklist
System access provisioning checklist
Tool training sequence
First 30 days task list
Buddy system documentation
Onboarding feedback form
Onboarding completion milestone in CRM
12
Operations Health Monitoring
Yutie monitors Operations metrics monthly and includes them in the Shalom Score. A domain that is not being measured cannot be managed.
Task completion rate (percentage of tasks completed on time)
Project on-time delivery rate
Bottleneck recurrence monitoring
Process adherence check (are SOPs being followed)
Tool adoption rate
Monthly Operations section in domain state report
Domain States
What each state looks like
in the Operations domain.
Every domain is classified monthly as Tending, Waiting, or Quiet. Here is what each state means specifically for Operations.
Tending
Work moves without the owner being the integration layer.
When Operations is Tending, every project has a structure, every task has an owner, every handoff is explicit, and the owner can see the state of all active work without asking anyone.
All active projects in the task management system
No critical work running on email or WhatsApp
Task completion rate above 85% monthly
Core workflows documented and followed
Owner can see full work status without status meetings
New projects started using existing templates
Waiting
System is in place, adoption is in progress.
Waiting means the Operations infrastructure has been built: task management configured, workflows documented, templates created. The team is learning the system and adoption is being monitored.
Task management tool configured and teams have access
Some projects in system, some still outside it
Core workflows documented, not yet consistently followed
Templates created for major work types
Automation built but some manual steps remain
Training done once, reinforcement ongoing
Quiet
Work is coordinated through memory, email, and messaging apps.
Quiet means there is no operational infrastructure. Work is tracked in heads and inboxes. Nobody has a clear picture of what is in progress, what is stuck, or what is at risk of being forgotten.
No task management system in use
Projects tracked in spreadsheets or not at all
Work handoffs happen verbally or by WhatsApp
No written procedures for recurring processes
Owner is the primary coordination point for all work
Files exist only in personal email or computer
New team member onboarding is informal
The transformation
What changes when this domain
moves from Quiet to Tending.
Before: domain is quiet or unmanaged
The owner is the integration layer, coordinating work that should coordinate itself
Projects are delivered late because handoffs between people were unclear
The same mistakes happen repeatedly because nobody documented how to avoid them
New team members take months to become productive because onboarding is informal
Nobody knows the current state of all active work without a status meeting
After: domain is tended
Work moves from stage to stage based on defined processes, not constant reminders
Every task has an owner, a due date, and a next action visible to the whole team
Recurring processes are documented so they produce consistent results every time
New team members onboard in half the time using structured checklists and training
The owner sees the state of all active work at a glance without asking anyone
Domain connections
How Operations connects to the other domains.
No domain exists independently. The Shalom Score reflects how each domain affects the others.
03
Relationships
Project delivery runs through Operations. The client it serves comes from Relationships.
05
Finance Visibility
Project completion in Operations triggers invoice generation in Finance Visibility.
06
Stewardship
Process documentation and file management in Operations are part of Stewardship's data integrity scope.
07
Intelligence
Operations metrics (completion rate, on-time delivery) feed into the monthly Shalom Score.