Let’s make chaos useful.
Bring me the
bottleneck.
Something in your business, organization, team — or even your own workflow — is harder than it needs to be.
- You don't have to know what's wrong.
- You don't have to know the solution.
- You don't have to know what kind of help you need yet.
Sound familiar?
Most operational problems don't look like problems from the outside. They look like workarounds everybody got used to.
- 01
Your team keeps doing something manually that feels ridiculous.
- 02
Nobody can find the information they need.
- 03
Training lives in somebody's head.
- 04
You've outgrown the spreadsheet.
- 05
People keep asking the same questions.
- 06
One person knows how everything works — and everything falls apart when they're unavailable.
- 07
Your systems technically work, but the process around them doesn't.
- 08
You've added people, tools, and technology, but somehow the work has gotten harder.
- 09
You think AI or automation might help, but you don't know where it actually belongs.
- 10
You have an idea but don't know what needs to exist to make it work.
If you nodded at even one of these, that's a conversation.
Consult with meSometimes the problem isn't complicated.
My onboarding is fucking crazy.
Call Aviyah.Nobody knows where anything is.
Call Aviyah.Why are we still doing this manually?
Call Aviyah.We have six spreadsheets tracking the same damn thing.
Call Aviyah.Every time that one employee is out, everything falls apart.
Definitely call Aviyah.
You don't need to know whether you need automation, AI, software, documentation, training, or a redesigned process.
You just need to know:
This shit isn't working the way it should.
That's enough to start.
Consult with meCuriosity before intervention.— Aviyah, founder
I don't arrive with a product to sell. I arrive with questions — and I ask them of the people who do the work, not just the people who designed it.
How I work
Seven steps.
No mystery.
Give me an operation. I'll learn how the humans actually do the work, find where the system is fighting them, and help design something better.
Understand → Identify → Redesign → Build → Validate → Implement & Improve → Document & Hand Off
Step 01
Understand
I learn how the work is done today. I talk to the people doing it, review the tools and documentation, and map what's actually happening — not just what the official process says should happen.
Step 02
Identify
I find the friction: extra steps, knowledge gaps, bottlenecks, repetitive work, communication failures, and the places where a small change would go a long way.
Step 03
Redesign
I redesign the workflow around the people who actually have to use it — their shifts, their access, their tools, their reality.
Step 04
Build
When it's needed, I build what supports the new process. Sometimes that's software. Sometimes it's a checklist.
Not every problem needs new softwareStep 05
Validate
The people who do the work help test it. Subject-matter experts stay the authority on specialized procedures and organizational knowledge.
Step 06
Implement & improve
We run it in the real environment, collect feedback, and adjust until it holds up under real conditions.
Step 07
Document & hand off
You get a practical playbook: how the new process works, how the system works, how to maintain it, and how to handle future changes. I don't need to own or control what I build. The goal is to leave you with something better than what existed when I arrived.
Step one is a conversation.
Consult with meWhat I build — when it fits
This is the toolbox.
Not the business.
I don't sell software. I improve the process and build what's necessary to make the better process work.
On AI
AI is a tool I use where it earns its place — sorting, summarizing, drafting, answering questions from your own documentation. I won't bolt it onto a process that just needs to be simpler.
AI-assisted systems
Practical AI built into a workflow, with people still deciding.
Automation
Data and notifications moving without a person in the middle.
Dashboards
One shared, current view instead of a dozen copies.
Internal applications
Lightweight tools for intake, tracking, approvals, and handoffs.
Knowledge bases
The answers in people's heads, written down and findable.
Training & onboarding
What people need to know, in the order they need it.
Documentation
SOPs and playbooks in plain English, with the why next to the how.
Checklists
Sometimes the smartest fix fits on one page.
A redesigned process
Fewer steps, clear owners, cleaner handoffs.
Websites
When the process starts with your customer.
Nothing technical at all
If the answer is a conversation and a clearer process, that's the answer.
The solution fits the problem — not the other way around.
Who I work with
Different rooms.
Same door.
Everyone who walks in has the same thing in common: something they're trying to make work better. Tap a room to step inside.
It doesn't matter which room you're in. Everyone starts at the same door.
Evidence
How I show my work.
Every engagement gets written up the same way, so you can see how I think — how the problem was found, how the process was redesigned, how it was validated — not just what got built.
The eight-part breakdown
This is the structure every case study on this site will follow. Confidentiality comes first: organizational details are protected, and what's shared is the method and the outcome.
- Room 01
The problem
What wasn't working?
- Room 02
The existing process
How was the work actually being done?
- Room 03
The gap
Where was the friction, risk, or knowledge problem?
- Room 04
The solution
What was redesigned or built?
- Room 05
Implementation
How did it enter the real workflow?
- Room 06
Validation & feedback
How did the people doing the work shape it?
- Room 07
The result
What measurably improved?
- Room 08
The playbook
How was it documented and handed off?
Case studies and evidence will be added here as the portfolio develops — each one written in this format, with confidentiality protected appropriately.
Who I am
Multifaceted.
On purpose.
I'm not a one-trick consultant. I never have been. I've worked at Google in global health and wellness leadership. I've worked in data center operations. I'm a certified CPR and BLS Instructor. I've published books. Built systems. Created frameworks. Started businesses.
And I've done most of it while figuring things out in real time — which is exactly why I can sit with you while you figure yours out.
It's not the things I did that gave me the experience. It's the preparation I created to get there.
I won't sell you something you don't need.
I won't pretend I can help with something I can't. And I will never make you feel small for not knowing what you don't know yet.
What it's called professionally: business process transformation, process improvement, AI-enabled process improvement, workflow and systems design, operational problem solving. What it feels like: the work finally makes sense.
What I believe
If you want to understand how work actually happens, talk to the people doing the work.
My very first time on an airplane, I decided I wanted to be a flight attendant. So I talked to flight attendants. I learned how the job actually worked — from the people doing it — before I was ever hired.
I was hired as a flight attendant twice. Not because I'd done it before, but because I got curious, adapted, and showed up as the thing before the thing even happened.
Every engagement still starts there: with the people who live inside the process.
How engagements work
Clear terms.
No surprises.
FreeFree conversation — you tell me what's happening. I ask questions. No clock running.
PaidPaid consultation — advice, direction, or a focused look at one process. Paid, even if it's one hour, even if we've known each other for years.
ScopedScoped engagement — my skills and time on the work itself. Scoped and agreed on before work begins.
The Vyb is open — but it has walls. Honest goals, ethical intentions only. Religion, illegal activity, and anything that violates someone's dignity are not on the menu. Not because I'm judging — because I know my lane.
☕ 🏢 💻 Your site, a coffee shop, or virtually.
The front door
You don't need a scope.
You need a starting point.
You don't have to know the scope — or what kind of help you even need yet.
- Tell me what's happening.
- Tell me what's frustrating you.
- Tell me what keeps breaking.
- Tell me what takes too long.
- Tell me what your team complains about.
- Tell me what you wish worked differently.
You don't have to diagnose it first.That's my job.