I started a blog you’re not supposed to read.

As a neurodivergent creator, I struggle to find my voice, see where I can make an impact, and stay focused on work that matters to me. AI helps me do all three.

Now I write posts you can hand to your AI so it can help you do the same.

A blog for your AI.

Visit my Substack

Building humanity emPowered by AI.

A marionette figure that has cut its own strings, rendered in dark tones

ABOUT RHO

Your business probably didn’t become complicated all at once.

If you lead a growing ecommerce, retail, or founder-led company, the systems that support the business probably grew the same way the business did:

One decision at a time. A new report got built because someone needed an answer. A new process was created because the old one couldn’t quite handle what came next. Someone figured out how two systems fit together. Someone else became the person who remembered why a metric was defined a certain way. Those decisions worked.

The business grew up.

I’ve spent my career inside this problem.

At Purple, I inherited a reporting environment with thousands of dashboards.

Rho Lall, a BI architect, in sunglasses against dark weathered timber

Eventually, I deletedover 2,000of them. They weren’t there because people were careless. They accumulated because the business was moving quickly and people were solving the problems in front of them.

A man pointing at a single point of light surrounded by hundreds of dark screens

I’ve seen the same pattern in code, data models, reports, spreadsheets, processes, and teams. The business grows. The systems grow with it. And eventually, nobody can see the whole thing anymore.

You may recognize some version of this.

You have a hundred models and regularly use a fraction of them. Different teams use slightly different definitions for the same number. A meeting that should be about making a decision turns into a debate about which report is right.

A process works because a few experienced people know how to make it work. Someone remembers why a decision was made three years ago, but it was never really documented.

The information exists.

The systems exist.

The people are capable.

But more and more of the business depends on someone remembering how everything connects.

That dependency gets expensive.

At first, it looks like inconvenience. A report takes longer to validate. A project gets delayed. Someone has to explain the same decision again. An executive becomes the person stitching it all together.

Then one of those people leaves. And suddenly the company doesn’t just lose a person. It loses the reasoning, history, and connections that person held together.

The questions get harder as the business grows.

Sales affects inventory.

Inventory affects warehouse capacity.

Returns affect finance, merchandising, operations, and the customer experience.

Marketing data needs to connect to what customers actually buy.

AI and automation create new possibilities, but they depend on information the business can actually trust.

At that point, another dashboard rarely solves the whole problem.

You need to understand what the friction is telling you.

That’s where I come in.

I’m a BI architect.

I work in the space between technology, data, business decisions, and the people who understand how the company actually works.

My job is to help make the hidden connections visible.

Sometimes that means simplifying a reporting environment.

Sometimes it means rebuilding a data model.

Sometimes it means documenting decisions that have been living in someone’s head.

Sometimes it means discovering that the technical problem everyone has been trying to solve isn’t really a technical problem at all.

I don’t start by gathering requirements.

A lot of technical projects begin with a seemingly reasonable question:

What do you want us to build?

The business is expected to describe the finished solution before anyone has really explored the problem. So everyone works hard to document the requirements. Then the solution gets delivered. And the conversation goes something like this:

“That’s not what I asked for.”

“But it meets the requirements.”

Both sides leave frustrated.

The business starts to feel like the technical team doesn’t understand how the business actually works. The technical team feels like it did exactly what was asked. And over time, the relationship gets worse.

Business teams learn that they have to be extraordinarily precise about every request. They start trying to design the solution themselves because they’re afraid that anything left ambiguous will come back wrong.

Technical teams become increasingly dependent on detailed requirements because that’s how success is being measured. Now the people closest to the problem are being asked to prescribe the technical solution, while the people best equipped to build the solution are being asked to follow the prescription.

I work differently.

I start with the person, the problem, and the pain it is creating. I research how the problem actually shows up in the business. Then I build something quickly. A prototype. Something concrete enough to react to.

A CFO once gave me the clearest explanation of why this works:

“Give me something to look at.”

That stuck with me.

People struggle to design a solution from a blank page. Give them something real and the conversation changes:

This part is right.

That isn’t what I meant.

What if we looked at it this way?

Now that I can see it, here’s what I actually need.

That feedback isn’t a failure of the requirements.

It’s part of discovering the solution.

Start by following the friction.

The process is simple:

  1. Start with something that feels harder than it should.A report nobody trusts. A process that depends on one person. A project that keeps stalling. A decision you can’t quite get comfortable with.
  2. Follow the friction.This is my ADHD superpower. I can chase all the rabbit trails, connect the facts, test assumptions, surface contradictions, and see the dependencies that lurk under the surface.
  3. Decide what deserves attention next.You leave with a clearer view of what matters, why it matters, and what needs a closer look.

Good systems preserve what works.

Growth creates pressure to formalize things. That doesn’t mean replacing judgment with process or turning a creative company into a bureaucracy. The goal is to preserve the knowledge, flexibility, customer understanding, and decision-making that helped the company succeed.

Build enough structure around those strengths that they can survive the next stage of growth.

You shouldn't have to be the one stitching it all together.

The decisions shouldn’t live in someone’s memory. The definitions shouldn’t depend on who happens to be in the room. The connections between teams, systems, and processes shouldn’t disappear when someone leaves.

The system should carry that memory for you.

It should preserve what was decided, show how the pieces connect, and make conflicting assumptions easier to see. So your people can spend less time remembering how the business works and more time thinking, creating, and deciding what comes next.

Rho reading in a chair beneath a saguaro in the Sonoran desert

What Can AI Take Off Your Plate?

It’s Friday. You have a pile of work that’s done and realize you haven’t thought about it all week. I’ll show you my setup to handoff work to AI, so you can finally move…

Getting Started with Claude Code

When you copy the answer out of ChatGPT. How much of your work is still left? You paste the answer back into whatever you were working on and pick up where you left off.…

This Dashboard Answers Everything Except Your Question

Something on the dashboard looks hinky. You ask one question. Not a hard one. You want to understand. But the asking becomes a process. People pulled in, then someone…

Another Meeting Lost To Internal Bickering

Some sales in our report were recorded the day before the session where they supposedly happened. That caused sales numbers to flicker slightly depending on what date…

We Don’t Do That Kind of Thing, Do We?

Did I ever tell you about the time that I exorcised a demon? I only ever saw the house at night. We would return, knock, wait, knock again, and move on. At the time that…

Railway is compromised.

This text from a buddy sent me into thirty minutes of rotating keys last night. “Railway is compromised.” This Substack is reader-supported. To receive new posts and…

How I Act On Questionable Numbers

What do you do with an expensive answer about your own business that you can’t sign off on? At Purple, our media mix model said marketing had zero impact on sales.…

Do you Catch Your Agents in Loops?

It’s October, and I’m still working on goals I set in January. Some of them feel new, until I read my notes. The same goal. The same excitement. The same promise to…

Hyper-growth Isn't Your Problem

We grew so fast. But now, there is all this stuff. Growth was the goal. Now when the numbers don’t match and the audit comes back dirty, it’s the thing everyone points…