The scale varied depending on the company and the complexity of the work, but the core process was remarkably consistent.

From finance to manufacturing to healthcare and health insurance, the specifics changed, but the foundational process stayed the same.

It started with a business problem that had to be understood, translated, and handed off to the technology team, or whichever group was responsible for building the solution.

What it used to look like:

For our work: It started with a whiteboard.

A big one, wall size sometimes. And a room full of people who actually did the work. Not the managers. The people doing the work.

Every phase had a name, a deliverable, and a confirmation step.

Here’s what that looked like from the inside.

Discovery and Process Mapping We’d map out every step using a framework called SIPOC: Suppliers, Inputs, Process, Outputs, Customers. Who feeds this process? What goes in? What happens? What comes out? Who receives it? It sounds simple. It never is. People who do the same job describe it differently every time. Most projects fail here because people describe the process they wish existed, not the one that does.

From those sessions came a process map — a confirmed picture of what actually happens, reviewed by the people who live it. That’s called current-state mapping. You have to know where you are before you can design where you’re going.

Requirements Gathering That map became a Business Requirements Document. Translating what people need into specific, written agreements. Not “we need a better system.” More like: a manager needs to approve a request within 24 hours and get a notification if they haven’t. Another round of confirmation. Sign-offs. Vague requirements produce systems nobody wanted.

Data and Logic Then a data model. Where does every piece of information live? Where does it come from? Where does it go? This is the invisible skeleton of any system. Skip it and you build something that works until it doesn’t.

Data Architecture and Database Design This is the database person’s work. They design the structure that holds everything — the tables, the relationships, the rules about what can and can’t be stored. They’re not writing the application. They’re building the foundation everything else sits on. Get this wrong and you’re rebuilding from the ground up later.

Application Development Then the application developers. They build the thing people actually touch — the screens, the buttons, the workflows. They work from the confirmed requirements and the data model. These are often different people with different skills, and the handoff between them is where requirements go to die if the spec isn’t airtight.

Prioritization At every stage, not everything could be built first. Prioritization is the discipline of deciding what’s essential now, what’s important later, and what’s a nice-to-have that will wait forever. Without it, scope wins every time.

Validation A dev environment first, isolated from real data. Then a staging environment with production data to surface what dev couldn’t. Then UAT — User Acceptance Testing — with the actual business users, not the people who requested the project. Because those are often different people with different definitions of “done.” Errors were tracked, routed through a tracking system or project manager, assigned to the right resource, fixed, and cycled back through dev and staging before being closed.

Change Management Every system touches people. Change management is the work of helping them understand what’s changing, why, and what it means for their day. The best-designed system fails if the people using it don’t trust it. This is the phase most non-technical founders don’t see coming. The system works. The adoption doesn’t.

Then, finally, go live. Followed by a hypercare period. Followed by the inevitable list of things nobody thought of until real users touched it.

Months. Sometimes years. Hundreds of hours before value was delivered.

The biggest hidden cost wasn’t just the time. It was scope creep — the slow expansion of requirements that happens when stakeholders can’t see the system until it’s nearly built. By then, everyone has new ideas. The change control process exists to manage that. It rarely wins.

What it looks like now:

Over the past few weeks, I’ve been meeting with clients.

Same process but done very differently - now I record them so I can stay focused on questions.

So no more whiteboard, no more worrying about my handwriting which was atrocious and looked more like chicken scratches.

I ran a working session structured around understanding the specifics around current-state mapping. I asked the questions that surface what’s actually happening versus what people think is happening.

That part isn’t the tool’s job.

It’s mine. Thirty-five years of sitting in those rooms gives you a feel for when a process description is accurate and when it’s aspirational.

(Sometimes it can feel mindnumbing and way too detailed for people)

When the meeting ended, I had a personalized summary document ready - a lightweight functional specification covering discovery, requirements, data, and prioritization in one pass. They reviewed it. Confirmed it.

That used to be multiple whiteboard sessions, then using an application called Visio to diagram it, and then the Business Requirements Document.

Multiple meetings, weeks of back-and-forth.

I remember the excitement of being able to take a picture of the whiteboard with my phone … that shortened my time (and I could erase the whiteboard)

Why Working Prototypes Change the Conversation

We did the same process that would have taken months in ninety minutes.

From that confirmed spec, I built a working prototype. Something they could click through and react to.

Humans are poor at validating abstractions.

They’re much better at pointing at something real and saying “not that.”

A working prototype collapses the user acceptance testing cycle — the feedback is immediate, and changes at this stage cost almost nothing.

Scope creep doesn’t disappear. It moves earlier, where it’s cheap.

And change management starts in that first meeting. When people can see what’s being built, they’re part of shaping it.

That creates a different relationship to the outcome than being handed a finished product. We can shape it together, up to a point, and then write clear specifications for what comes next.

In my experience, some of the most useful things we build could not have been fully defined ahead of time. They only became visible through conversation.

My excitement is about whats possible

Not the hype. The real business value that can now be created at a cost that would not have been realistic five years ago. Not building applications - systems.

What changed is the compression of the distance between an idea and a working solution.

Rapid Application Development has been a concept since the 1990s. What is different now is that the tools to actually deliver it, quickly and without a full development team, are finally accessible.

The people who stand to benefit most are not large companies with established IT departments.

They are founders and operators building systems to serve more people. The nonprofit that needs something practical. The small business owner who cannot absorb a six-month development cycle.

The tools did not replace the discipline.

Mapping the data and workflow is vital.

A confirmed picture of where we start before we design and where we're going still matters. A spec everyone has signed off on before anyone builds anything still matters.

After decades of building systems the long way, I can tell you: the work was always the clarity. The tools just finally caught up.

Which is why I’m so excited at what’s possible now - helping people leverage technology brings me great joy.

If you want to explore a project together, I’m offering 15-minute Clarity Sessions to see if we’re a good fit.

Take care,

Carolyn

On my worst, most ungrounded, lower-powered days, I am paralyzed by fear of what other people think of me to the point where sometimes I can’t breathe.

On my best, most grounded, plugged in to a higher power days, the slogan - “what other people think of me is none of my business” - keeps me moving when staying still would be easier. It frees me from chasing approval I don’t need and can’t control.

One exception.

What I've taught AI about me?

hat's my business. Technology is how I serve.

Context is how technology works best.

Here’s what I did.

I uploaded years of my published writing to my AI tools. LinkedIn posts. Facebook posts going back two or three years. Every publisher’s letter I’ve written for Journey Magazine. Emails I’d written that captured how I think and communicate. Real examples of how I actually show up in words.

Then I asked both Claude and ChatGPT to do one thing: summarize what they saw.

Not what I intended. Not what I hoped. What was actually there — patterns, tone, voice, the words I reach for, the ones I avoid. A baseline drawn from ones and zeros. No preconceived judgment. No colleague softening the feedback. Just: based on everything I’ve provided, this is what I sound like.

That summary became the foundation. A core document that reflects my actual voice and not an aspirational version of it.

That was quite humbling, honestly.

I use both Claude and ChatGPT, and the way I load context into each is different. But the intention is the same. I keep adding to it as I grow. As my communication gets sharper, the context gets sharper with it. It doesn’t drift toward generic because I don’t let it go stale.

This is about deciding that AI needs to know who I actually am — so it can support the work I’m actually doing.

Tools guess when I don’t provide context.

Every AI tool builds a working picture based on what I put in front of it. If I give it nothing, it fills the gap. It guesses from the middle. It writes for a generic founder, a generic advocate, a generic professional with some relevant experience. It smooths out the edges that make my work mine.

I’ve been publishing Journey Magazine since 2019. I have a voice. I have frameworks and bluepritns that keep my work consistent. I have specific things I will not say and specific things I always say. None of that shows up automatically. I have to put it in the room.

So I do. Now, both tools have the relevant context always. My voice. My editorial rules. Event my personal background history that is already public for when it matters.

The result is completely different from what I get without it. Not because the AI is smarter. Because it has actual information to work from instead of assumptions.

Layer 0.

I hadn’t written down who I am in a way a tool could use. I knew my voice when I heard it. I knew when something sounded wrong. But I hadn’t built a single source of truth for myself that let a tool know those things too.

That was the gap. And closing it started with one simple — but time-consuming — move. I pulled together a real sample of my own writing. LinkedIn posts. Facebook posts. Blog posts. Publisher letters. Emails. Published articles. I pasted it all in and asked the tool to summarize my communication style, my tone, and the patterns it noticed. I didn’t prompt toward an answer. I just asked what was there.

Technology changes at the speed of light. Context doesn’t. It has always been the most important thing — in every system I’ve ever built, in every tool I’ve ever used. In other tech systems it looks like Settings or Preferences or Standards or a Template. In AI it looks like a single source of truth file that tells the tool who it’s working with.

That file is Layer 0. It’s Carolyn. Just Carolyn.

Everything else builds on top of it.

Journey Magazine has its own voice and is a culmination of the team of people who have helped shape it: mission-driven, hope-centered, recovery-focused.

PracticalTech Advisory is just starting and the voice will evolve but from my tech background it’s starting with: plain-language, anti-hype, clarity-first.

Those “source of truth” files live in their own projects. But they sit on top of Layer 0.

Because no matter which hat I’m wearing, it’s still me wearing it.

The system only works because the foundation is solid.

One thing I never forget.

Everything that comes out of these tools is a draft. Not a final. My eyes are always on it.

AI can match my patterns. It can hold my frameworks. It can write in a register that sounds like me. What it cannot do is know what I mean to say on a particular day about a particular thing. It can’t carry 30 years of lived experience into a sentence. It can’t decide what’s true right now versus what was true six months ago. It can’t know what I’m ready to say publicly and what I’m still sitting with. It can’t feel the reader the way I do.

That’s still mine. All of it.

The goal was never to hand ALL of the work over.

The goal is to hand over the appropriate type of work that computers can do — the mechanical, the repetitive, the first draft that used to take me an hour.

What I keep is the voice, the judgment, and the final call. A tool that has my “single source of truth” gets me to a strong draft faster. A tool working from nothing gets me something I have to rebuild from scratch.

The principle is the same one I learned in recovery.

I can’t let someone else define me.

But I also can’t expect anyone to know me if I’ve never told them.

That’s true of colleagues, partners, and communities. It turns out it’s also true of the tools I use to do my work.

I spent 25 years in corporate IT hiding who I was. I put on armor every morning and never let my actual history into the room. I know what it costs to be invisible in a space where I’m trying to do good work.

Helping people use technology better is what brings me joy. It always has.

I’m not interested in being invisible to my own tools.

Grateful.

My work gets better when I stay with what is mine to do instead of measuring myself against people whose strengths are easier to see.

That is what I hear in “Lose yourself in the music, the moment …” — a call to commit fully, stay present, and stop looking sideways.

For a long time, I measured myself against people whose strengths were easy to see.

Some were more visible. Some were more polished. Some seemed naturally built for the kind of leadership that draws attention quickly and holds it. Some knew how to speak with force and certainty in public. Some knew how to move a room.

Some seemed to arrive already shaped for the work they were doing.

And being a lifelong learner, YouTube gave me plenty of input about how to fit that mold. There were always people suggesting early morning cold showers, deep work, only three things on your to-do list. Amy Porterfield was probably my first “wow, I wish I were that organized” fan-girl infatuation, but there have been dozens more since. I watched what they did. I tried to fit it into my life.

And ultimately, unsurprisingly, it did not work for me.

But over time, I have spent less energy comparing myself to people with different strengths and more energy trying to understand my own. That shift has changed the way I think about work, contribution, and where I can be genuinely useful.

I’ve spent less time asking whether I look like the right person for the work, and more time asking where I can be genuinely useful.

That question now carries more weight for me than image, style, or whether my path looks familiar from the outside. It has also helped me see the deeper connection between in the work I care most about right now: Journey and PracticalTech.

On the surface, they are not the same.

Journey is rooted in recovery, visibility, and making support that already exists easier to see.

PracticalTech is rooted in systems, decision-making, and helping people use technology more thoughtfully.

But for me, they come from the same instinct.

I am most useful when I turn friction into clarity.

I’m most useful when I help people see where practical technology can reduce friction and create more room for the work that feels most important to them.

That has been true for longer than I understood. I am usually at my best when I can take something that feels tangled, abstract, or overwhelming and make it more understandable.

I’m a dot connector who gets real joy from helping others.

Sometimes that means language. Sometimes that means structure. Sometimes that means strategy. Sometimes that means helping someone see that the next step is smaller and more practical than it first appeared.

In PracticalTech, that often means helping founders, leaders, and teams think more clearly about the role technology could play in their work.

That kind of work appeals to me because it is grounded in practicality.

It’s not about technology for its own sake. It is not about chasing tools, trends, or complexity. It is about using the right systems in the right way so more energy can go where it will make the most difference.

Journey comes from a similar place, even though the subject matter is different. The work there is not only about recovery itself. It is also about visibility, language, and reducing the kinds of friction that keep people from recognizing support. In both cases, I keep returning to the same basic task: make things easier to see, easier to understand, and easier to move toward.

That realization has also changed the way I think about mindset.

For me, presence means staying with the moment in front of me and meeting it fully. Not drifting into comparison. Not getting lost in performance. Not trying to adopt someone else’s voice because it appears more effective from a distance. Just staying clear on the vision and acting from what is actually mine to do.

That is harder than it sounds.

Comparison can feel productive because it creates the illusion of calibration. It can look like ambition, discernment, or high standards. But for me, it often becomes a leak. It drains attention away from the work itself. It creates noise where clarity is needed. It tempts me to shape myself around someone else’s strengths instead of deepening my own.

The older I get, the more I value precision in where energy goes.

I’m not interested in being the loudest voice in the room; I care more about building things that help people move with clarity.

That feels especially clear to me now. There is already enough noise. Enough performance. Enough pressure to appear certain, visible, and fully formed at all times.

What I care most about is usefulness.

What I care more about is whether something I build, write, clarify, or structure actually helps another person move forward with a little more steadiness and a little less confusion.

A few questions have stayed with me lately:

• Where does effort feel most natural and most generative?

• What kind of work keeps producing clarity instead of depletion?

• Which strengths are real, even if they are quieter than someone else’s?

• Where has comparison become a distraction from contribution?

• What would it look like to trust the shape of my own work more fully?

I don’t always have neat answers to those questions.

But I have found them more useful than the old habit of looking sideways and trying to determine whether I resemble the people I admire.

Admiration still has value. Learning from others still has value. Taking insight where it is useful still has value.

But imitation is something else. So is chasing someone else’s definition of productivity, efficiency, or success. It pulls attention away from what is true and shifts the work from grounded contribution toward performance.

Imitation asks for performance.
Real work asks for presence.

That is what I’ve learned from Lose Yourself: stay with the moment, stay with the work in front of me, and stop measuring myself against what was never mine to carry.

I want more real work because the work that lasts is the work that fits in my unique hands.

Grateful for my own clarity.

Carolyn

Working with my coach, she asked me a simple question: who has influenced me?

At first, I expressed disdain at the word; which being who she is, caught the look.

So we talked about it … and she expanded my perception of the word itself.

To influence means to flow into. That felt very different from the version of influence I usually react to online.

It felt quieter, more relational, more subtle.

At first, I thought about online influencers, people I followed, people I bought courses, ideas, and frameworks from, and I could feel myself react to the term. I have learned that part of that reaction came from recognizing how often, when I was not clear, I looked outside myself for someone to hand me a framework for how to work, live, or move forward.

So it brought up the usual images: big, bold, loud, highly visible, always projecting something outward.

But as I sat with the question longer, I realized the real influencers in my life have been nothing like that.

They have been quiet, subtle, and steady. They have influenced me less through performance and more through presence. Less by telling me who to be, and more by helping me come into deeper alignment with myself, my own gifts, and what I am here to bring to the world.

Influence is quieter than I thought

That realization also helped me make sense of this past year.

Over the last year, my world got quieter.

I let in fewer outside voices suggesting how to work, how to think, how to start my day, how to organize my desk, my files, my business, my life. I stopped reaching so quickly for someone else’s system, someone else’s language, someone else’s answer.

And as that noise dropped, my mind got quieter too.

I could hear guidance more clearly. I began to trust my own intuition because I was anchored. I could notice what actually gave me energy, what created friction, what felt performative, and what felt true. I became less interested in borrowing a way of being and more interested in paying attention to my own life.

That quiet has led me to interesting rooms - people I can learn from but not assume their way of being is better than my way of being (and then hurt myself with myself when their way doesn’t work for me)

In 12-step rooms we call it “being a worker among workers”

Quiet creates clarity

In that quiet, I learned a few important things.

I need to find my own way of doing things. I need to define what is working for me now, not in theory, but in this actual season of life, and assess it honestly each week. And I need to keep asking a simple question: am I doing the things I say are important? Am I keeping the promises I make to myself? Am I being a helpful cheerleader to my own internal voice?

What has come from that is real.

I trust myself more. I invest more in what actually nurtures me. I feel less pulled by other people’s systems and more anchored in my own life.

Sometimes the clearest way forward is not to add another system or voice, but to get quiet enough to notice what is already true for you.

The work became clearer too

That shift has shaped my work, too.

With Journey, the mission has always been to make recovery more visible. What we have found is that quiet conversations in communities about the free resources available are often what amplify that hope most.

With PracticalTech, I want to help the people “who help the people” better use technology in ways that actually support their work. Not more noise, not more complexity, but tools and systems that create clarity, capacity, and real usefulness.

What influence means to me now

So when I think now about influence, I think about discernment. Less about what voices I let in, and more about protecting my own energy. More about getting in rooms with people who value that kind of quiet and support one another in aligning daily actions with what matters most to them individually—and in some almost magical way, that creates energy that supports all of us.

What I am learning is that when I get quiet, find my people, and stay aligned, I am much better able to leverage my own skills and expertise in support of my primary aim: to be of service. The people who have shaped me most are the ones who helped me get quieter, clearer, and more honest about what I am here to do.

They are the ones I can feel in my heart and anchor to in the quiet of the morning.

Grateful for this bonus life.

Most teams don’t have a software problem. They have a context problem that the tools are quietly amplifying.

If your team feels maxed out but output isn’t moving, it’s usually not because people aren’t working. It’s because the system requires too much human glue: chasing missing inputs, translating between tools, reconstructing decisions, reformatting the same data in three places.

That’s not “busy.” That’s overhead.

Tools don’t create leverage. They scale whatever you already have.

A tool can’t supply intent. It can’t resolve disagreement. It can’t replace a definition of “done.” It only accelerates the underlying structure.

So if your operating model is unclear, a new platform doesn’t fix it. It just increases throughput of the confusion.

Complexity is the silent killer (because it hides context)

Most operational friction lives below the waterline:

• tribal knowledge living in people’s heads

• unwritten rules that only show up when something breaks

• silos that force manual handoffs

• process gaps patched with workarounds

• multiple “sources of truth” that drift

That hidden context is what makes stacks feel heavy. Teams spend their energy navigating the system instead of producing results.

Complexity isn’t just annoying. It’s capacity-consuming.

Tools can’t fix that. They only scale it.

The fix isn’t “simplify your tools.” It’s make the work explainable.

The way out isn’t another app. It’s an architecture shift:

1. Start from the output (one observable definition of “done”).

2. Work backward to required inputs (what must be true for that output to exist).

3. Design capture at the edge so inputs arrive complete and structured.

4. Assemble context at the moment of work so nobody has to hunt.

5. Then automate the execution steps.

This is the part most teams skip. They automate a manual process and end up with an automated version of the same inefficiency.

Outcome-first beats vendor-first

Stop asking “What tool should we use?” and start asking:

• What output are we trying to produce reliably?

• What inputs are required every time?

• Where should each input live?

• What gate prevents incomplete work from entering the system?

• What record assembles context so execution starts with clarity?

Once you can answer those, the stack becomes obvious. And if the tool changes later, the system still holds.

What “practical leverage” looks like

When it’s working, you’ll notice:

• fewer handoffs require meetings

• fewer tasks depend on memory or heroics

• work begins with a complete packet, not a scavenger hunt

• “status” is readable from the system, not from a person

• changes don’t collapse the whole workflow

That’s not productivity theater. That’s a system that does what a system should do - free up humans to make decisions, do judgment work, and move the work forward—without acting as the integration layer.

Quick diagnostic questions

If you want to pressure-test your stack, use these:

• New hire readiness: Could a new person run the workflow in week one using only what’s documented and stored in the system—without needing someone to explain how it really works … now?

• Handoff resilience: If the owner is unavailable for two days, can someone else pick it up from the system record and complete it without a meeting?

• Capture once, reuse everywhere: Is information captured once at the start in a structured way, then reused downstream—or does it get recopied and reformatted across tools?

• Change tolerance: When something changes (a team member, a tool, a client variation), does the workflow still run—or do people have to patch it with exceptions and manual work?

If these questions are exposing gaps, there’s usually an opportunity to redesign the workflow so the system carries more of the load and people do less coordination work.

After decades sorting through operational chaos and turning it into systems that hold up under real conditions, I can help you do this without adding more tools, more meetings, or more workaround layers.

If you want to map one workflow and identify the smallest changes for leverage, book a 15-minute clarity call.

Let’s talk!

Enjoy your day!

Carolyn

Now consider the quiet assumption inside that statistic:
You only “meet criteria” if you’re willing to sit in front of someone and be evaluated.

Many people won’t.

Not because they don’t know something is wrong.
But because diagnosis creates a record.
And a record can follow you - to insurance underwriting, life insurance applications, professional licensing, custody disputes, security clearances.

Stigma isn’t just social. It’s structural.

So when we say “1 in 6 meet diagnostic criteria,” we are describing only the people willing to risk being counted.

The rest remain invisible.

Those who are struggling, even suffering (and honestly maybe dying) but the risk is too high to reach out for help if the only path they see requires being "assessed and counted".

A system that requires visibility in order to qualify for help - while simultaneously punishing visibility - will always undercount the people who need the care.

AND on the visible recovery side, given the millions in 12-step programs, we don't "count" them ....

Maybe if we assume that :
If normalizing the conversation, signaling that it’s safe to ask for help, and offering clear, free pathways to support helps even one person reach out before a crisis becomes a catastrophe - that's a big damn deal.

That is the point.

That is impact.

Yesterday, the realization stopped me in my tracks because the problem felt overwhelmingly large and I had to set my research aside.

This morning, after a good night’s sleep, time in prayer, and conversations with wise friends, I see something different.

Not just the scale of the problem, but the scale of the opportunity.

Grateful for my bonus life.

source:
* SAMHSA — Release of the 2024 National Survey on Drug Use and Health (NSDUH) (reports 16.8% / 48.4M with past-year SUD).

That pause wasn’t about slowing down. It was about setting up an environment where the work is explainable.

The same principle applies to operations.

The goal isn’t to document the Messy Middle in all its nuance. The goal is to use tech to make the space between inputs and outputs behave—so work and data flow without relying on memory, heroics, or retyping.

So here’s the operational version of what I’m building in my “teaching systems”:

Start from the output. Work backward. Identify every required input. Then use tech to capture, route, and assemble those inputs so the middle becomes lighter.

Not automated busywork. Leveraged flow.

The Middle Is Not the Problem. It’s the Opportunity.

Most operational friction lives in one place:

the distance between what comes in and what needs to go out.

• inputs arrive incomplete, inconsistent, or scattered

• outputs require standards, checks, and context

• humans become the glue layer: interpreting, chasing, translating, reformatting

That glue work is what people call “the messy middle.”

But I’m less interested in naming the mess than in designing a system where the mess doesn’t matter as much.

Because tech is good at exactly the parts humans shouldn’t be doing:

• capturing structured inputs

• maintaining state

• moving data between tools

• assembling context at the right moment

• enforcing completeness before work begins

That’s the middle doing work.

Don’t Automate a Manual Process. Rebuild It Around Leverage.

A subtle trap: taking a manual process as “truth” and trying to automate it.

That usually produces an automated version of the same inefficiency.

A better approach is:

1. define the output (what “done” looks like)

2. work backward to discover required inputs

3. design the flow so tech carries the load

4. only then automate execution steps

This is why I don’t start with, “What can we automate?”

I start with, “What output are we trying to produce reliably—and what inputs does it actually require?”

The Output-Backwards Method

Pick a single output you want to make repeatable. Ops-focused examples:

• a client onboarding package is complete and delivered

• a weekly reporting packet is produced and sent

• a deliverable ships with QA passed and files stored correctly

• a support request is resolved with documentation updated

• an internal handoff is completed with all context attached

Now work backward in a specific way:

Step 1: Write the “Definition of Done” (DoD)

One sentence, observable, not vibes.

Example:
“Onboarding is done when the client has confirmed access, baseline data is collected, kickoff notes are stored, next milestones are scheduled, and ownership has moved to delivery.”

This is not documentation for documentation’s sake. It’s your target spec.

Step 2: List the required artifacts

What must exist at the end?

• links, files, records, confirmations, dates, IDs

• not “tasks,” but artifacts that prove completion

Artifacts are where tech shines because they’re trackable.

Step 3: For each artifact, ask: where does it come from?

This is the key move: you’re not mapping nuance—you’re identifying inputs.

• Who provides it?

• What system should hold it?

• What format should it be in?

• When should it be captured?

You end up with an input inventory.

Step 4: Design input capture so it’s hard to be incomplete

Instead of relying on people to remember what to include, you set up capture points:

• a form with required fields

• a CRM stage gate

• a templated intake doc

• a structured support ticket

• a checklist that blocks advancement without the artifacts

The goal: completeness becomes a property of the system.

Step 5: Use tech to assemble context at the moment of work

This is the real leverage in the middle.

When someone begins the work, they shouldn’t have to hunt.

Tech should pull together:

• the intake answers

• the latest status

• related files and links

• key decisions and constraints

• owner + due date + next action

This can be as simple as a “single source of truth” record that gets updated automatically, or as advanced as an AI layer that composes a brief and flags what’s missing.

Either way, the middle becomes lighter because context is pre-assembled.

Where AI Fits (Not as “Automation,” as Infrastructure)

AI is useful here when it supports flow:

• Normalize inputs: turn messy notes into structured fields

• Extract requirements: pull key constraints from emails/calls into the system

• Generate briefs: create a clean work packet from scattered inputs

• Flag gaps: detect missing artifacts before the process advances

• Summarize state: produce “where things stand” from the record

This isn’t “AI replacing humans.”

It’s AI making sure humans aren’t doing integration work with their brains.

The Middle Becomes a Lever When You Treat It Like a Data Problem

When you work backward from output, you stop thinking in terms of “tasks” and start thinking in terms of:

• required inputs

• required artifacts

• state transitions

• quality gates

• system ownership

That’s why this approach scales cleanly: it’s not dependent on any one person being careful.

It’s dependent on the system being designed to collect what it needs.

That’s the foundation move again.

The same reason I’m building teaching systems before I go daily: I want a base where the work is explainable, transferable, and repeatable.

Reference back to the earlier post

In Staying With the Messy Middle, I shared the shift that helps me most: using AI to interview me like a new hire—so clarity forms before I try to standardize anything.

This output-backwards method is the operational companion to that.

Instead of “tell me the SOP,” it’s:

• “Here’s the output.”

• “What inputs must be true for this to exist?”

• “Where should each input live?”

• “How do we capture it once, cleanly, at the edge?”

• “How do we assemble it so work starts with context?”

Clarity first. Then leverage. Then automation.

Call to action

If you want to apply this to one operational flow in your business, I’m offering 15-minute Clarity Sessions to see if we’re a good fit—and whether I can support you in designing it.

Take good care,

Carolyn

February 12th was the day I accepted that as an alcoholic and drug addict, I was going to need help and support to change the direction of my life — and I entered a long term treatment program for women.

Six months later, I went to McAuley Residence — a structured program that gave me the guidance and support I needed to reunify with my children. That experience became the foundation for everything that came after.

My primary aim has remained simple: to be of maximum service to my fellows.

As I started living the life of a sober woman — mum, sister, worker, wife — sobriety didn’t remove complexity. It asked me to face it differently.

That requires keeping my own path clear (with help from a higher power and friends). If I’m scattered or forcing solutions, I’m not actually useful. I’m just busy — and busy is not the same thing as being of service.

The 12-step framework works best when I show up honest about where I am and stay open to help. From that place, real solutions are able to emerge — an intuitive thought, clarity, community, and practice.

Sometimes the real work is subtraction, not addition. And right now, that clarity is pointing me away from something I thought I should be doing.

What New Information Taught Me

Here’s what’s become clear: posting daily 5-minute tool tips videos are not my direction right now. Technology shifts too quickly. A single “how I use it” expires almost as soon as it’s published. The pace creates pressure, and pressure is not the same thing as purpose.

The ironic part? I’ve always known tech changes fast. We used to call it the “bleeding edge” when exploring new technologies too quickly. The rate today is minutes, not weeks — but I stepped down that path anyway.

The pressure to constantly produce doesn’t match the lasting value.

What does last is how we think about technology.

How we evaluate tools before bringing them into our workflows. How we decide what to automate and what deserves human attention. How we design systems that reduce friction instead of adding to it — that improve accuracy, free up mental energy, and create space for the work that requires our full presence: building relationships, making judgment calls, serving others, creating something meaningful.

Technology’s real value isn’t in the latest feature. It’s in giving us back time, clarity, and capacity to focus on what can’t be automated.

That kind of thinking doesn’t expire with the next software update.

So I’m adjusting my sails — less production for visibility’s sake, more attention to the deeper work that actually helps people and keeps me grounded.

The Same Practice, Different Context

The fellowship taught me something fundamental: I don’t have to figure things out alone. I can say where I’m stuck. I can listen to people who have walked ahead of me. I can take the next right step without seeing the entire staircase.

That same method is how I learned to build a business I love.

And it’s how I’m navigating this shift, too.

I don’t need to know the full plan. I need to do the next right things:

• Stop publishing daily tool tips that don’t serve my actual direction

• Show up in founder communities and mastermind groups where I can share what I’m building and learn from others

• Write about the thinking behind my tech decisions, not just the tactics

• Let the next steps emerge through honest conversation and lived practice

Recovery Framework → Business Framework

Recovery and business have more in common than we usually admit.

Both require:

• A clear primary aim (what you’re here for)

• Daily practices (what keeps you steady)

• Honest inventory (what’s actually true)

• The humility to revise the plan when reality changes

In recovery, my aim stays steady while my plan evolves. In business, it’s the same: I keep the compass fixed, adjust the sails, and stay in community long enough for the next right action to become obvious.

My aim stays fixed: be of maximum service, and keep my path clear so I can actually be useful.

My plan is allowed to change.

Right now that means stepping away from daily tool tips and focusing on the deeper thinking that helps non-tech founders navigate technology choices without the hype — trusting that the next steps will reveal themselves the same way they always have: one honest conversation at a time.

New Information, Same Compass

I’ve held onto plans that no longer fit what I’ve learned — about myself, business, capacity, actual impact. I’ve mistaken consistency for commitment and confused momentum with meaning.

I’m not failing when I change direction. I’m incorporating new information.

The compass stays fixed. The sails adjust. The process works.

If you’re in your own season of course-correcting — especially around tech, AI or data/workflows — I offer 15-minute Clarity Sessions.

No pitch. No upsell.

Take good care,

— Carolyn Delaney

As I started working toward the daily Loom videos I committed to—short, practical looks at how I use technology—I realized that the tech environment I live in every day isn’t the environment most people live in.

It’s layered. Some of it is paid. All of it was built through daily, practical use.

Comfortable to me, but not automatically accessible or repeatable for others.

That awareness brought up a familiar question:

Am I showing the thing—or am I accidentally showing the gap?

Backing Up to Build a Foundation

So before going daily, I paused.

Instead of recording right away, I went back and started laying a shared foundation: a couple of free, accessible environments that anyone can step into without cost or special permissions.

This isn’t a delay.
It’s preparation.

It’s the same move I’ve learned to make with technology over and over again: don’t build on top of something shaky. Slow down. Make the base explainable. Then layer.

These environments aren’t my real systems.
They’re teaching systems.

They let me show how I think, how I decide, and how I work through uncertainty—without asking anyone to start where I ended up.

That choice felt very familiar.

It felt like the bench.

The Pattern I Keep Relearning

What the bench taught me wasn’t how to write better.

It taught me how to show up consistently while something was still forming.

Right now, that’s what I’m doing with this tech work.

I’m not publishing daily yet.
But every day, I’m making progress on the foundation.

That is the practice.

And it mirrors exactly how I’ve learned to work with technology: steady, cumulative, inside-out.

The Clarity Bottleneck

This same pattern shows up clearly when people work with AI.

Having the tools isn’t usually the problem.

Clarity just hasn’t had a chance to form yet.

So they prompt.
Re-prompt.
Then assume the problem is the wording,
or that the technology is overhyped.

Or they assume they don’t know what they’re doing—and get frustrated.

Usually, the problem is that they’re standing in the messy middle of their own thinking—because it’s a normal part of learning something.

Letting AI Help Build Clarity

One small shift helps me.

Instead of asking it to give me answers, I sometimes ask it to interview me.

For example, when I want to document our fulfillment process, I ask the AI to act like a new employee—someone smart, curious, and unfamiliar with how things work here. The goal isn’t speed or polish. It’s to make the process clear enough that it can become a standard operating procedure.

I set the stage by naming four things:

• Role: act as a new hire learning our fulfillment process

• Goal: document the process clearly enough to hand off

• Format: ask one question at a time

• Boundaries: no more than 15 questions, stay on fulfillment, question my understanding before moving on

That’s the structure.

The AI starts by asking where the process begins and what “done” looks like. As I answer, each question builds on the last—filling in tools, handoffs, decisions, and edge cases—until the whole process can be mapped end to end.

When I catch myself thinking, “I should be able to explain this, but I can’t yet,” this interview process helps.

When I’m thinking, “I just need the answer,” it probably doesn’t.

Used this way, AI becomes a place to build clarity, not perform certainty.

Not Useful in All Cases, but …

This interview approach works best when I’m trying to:

• Clarify messy thinking when I know something’s wrong but can’t yet name it

• Surface assumptions I didn’t realize I was making

• Untangle decisions that feel emotionally or cognitively loaded

• Turn lived experience into language I can actually work with

When clarity is the missing ingredient, it’s one of the most reliable tools I’ve found.

Foundation Before Fluency

This is why I paused the videos.
This is why I’ll rebuild my examples using free tools.
This is why I’m moving deliberately instead of quickly.

First comes a foundation I can stand on.

Working from the inside out often looks messy on the outside.
That doesn’t mean the work isn’t working.

It usually means something is being built properly.

Staying in Motion

The daily videos will come.
They’ll get smoother over time.

For now, the commitment is simple:
show up, make progress, and keep the foundation solid.

That’s how I learned to work with technology.
It’s how I learned to trust myself.

Doing things roughly doesn’t mean something’s wrong.
It usually means something real is taking shape.

So for now, I’m staying with the foundation and letting clarity form as I go.

If you’re in a similar place—early, unclear, or standing in your own messy middle—I offer 15-minute Clarity Sessions.

They’re short, focused conversations to help you name what’s actually going on and find a next step you can stand on.

Take good care,

Carolyn

Decades ago, my friend Richard K shared his experience of learning new things by saying of course it’s going to be messy, but we learn.

It became a kind of permission during a time when everything in my life was new. I was newly sober, living in a women’s halfway house, and even brushing my teeth every day was something I had to relearn.

Over the years, it’s become something more permanent—a reminder that learning has a messy middle, and that sharing while I’m learning requires me to trust.

Sharing Daily

As I started to think about creating daily, helpful videos about technology, I found myself reflecting on this well-worn path of giving myself permission to be myself—staying with the messy middle even when it feels uncomfortable—and how it has served me well.

Today, the reminder is …

It’s not about being polished.
It’s about showing up while things are still forming—and following through on a promise I make to myself.

I learned the amplifier effect of me doing growing edge things daily.

I didn’t learn it from a youtube video, I learned it from a bench.

My Bench Project

During early covid, writing my Publisher’s Letter every other month was painfully time-consuming and emotionally hard. So much was happening, and every time I sat down to write, I froze.

I cried a lot during that process.
And it brought up a familiar chorus of who do I think I am thoughts—which, as it turns out, aren’t very helpful when you’re trying to write.

After talking it through with a fellowship friend, a few things became clear.

• I was agonizing over every single word.

• I wasn’t sharing regularly, so it didn’t feel like a practice.

• I was trying to say something more polished—grammatically and editorially—than my personal experience could support.

• And I had never been a journaler—I hadn’t written consistently before starting Journey.

Underneath all of that was fear.
So much fear.

I was given a simple suggestion: treat writing and sharing the way I learned how to meditate.
As a daily practice.

So I did.

What started as a practice slowly became a ritual.

Every day, I went to the ocean and sat on a bench (and usually took a picture).

I’d take a deep breath, say a simple prayer—usually just help—close my eyes for a few minutes, and then wrote about whatever was right in front of me. What I saw. What I noticed. What I was thinking.

And then I shared it.

No strategy. No audience building. Nothing planned.
Just me trying something new—visibly.

Just showing up.

What surprised me wasn’t that my writing improved. (although it did)
It was that the fear softened.

It helped me organize my thinking. It helped me say things more clearly. Over time, writing became something I loved instead of something I avoided.

Sharing daily took the pressure off.

There’s something powerful about sharing experience as it’s happening.

It offers a quiet kind of core strength—especially when things feel uncertain.

Working from the inside out can create a messy outside for a while.
That doesn’t mean the work isn’t working.

If I’m growing personally, there’s always newness.

There’s always another edge where things feel unfamiliar.

Especially now.

I’ve made a commitment to myself to record and share short Loom videos daily, showing how I’m using technology in practical, real-world ways. Not polished tutorials. Not perfect systems. Just what I’m doing and what I’m learning along the way.

The process of making the videos will be bumpy for sure.
I’ll learn how to explain things better, how to record more smoothly, how to make the process easier over time.

That’s part of the point.

I won’t be on camera much but you’ll hear my Maine accent and I’m sure I’ll laugh at myself more than a few times as I find my personal flow.

I’m sharing experience, strength, and hope the only way I know how—by showing up and staying in motion.

Roughly doesn’t mean something’s wrong.
It usually means something’s forming.

If you’re finding your footing too, you’re welcome to follow along and maybe try something new for yourself.

Here’s my first one - using NotebookLM as a critic to help me laugh at myself and improve the way I communiate.

https://practicaltech.online/try-this-today

Take good care and enjoy your day!

Carolyn

What matters to me just as much as capability is how we choose to use it. For the first time, technology can carry the messages that sustain humanity—connection, dignity, understanding, and care—without getting in the way.

I’ve been optimistic about technology my entire career. You don’t spend decades in IT if you’re a cynic—especially in the early years, when learning meant reading manuals, relying on trial and error, and failing in real time, long before technology made things easier for the people building it. I stayed optimistic because even then, progress was visible, messy, and absolutely worth the effort.

I’ve always believed progress was possible, even when the path was messy and the learning curve unforgiving.

I’m completely self-taught—through books, trial and error, mentors, and eventually the internet and YouTube. That freedom meant I wasn’t tied to a prescribed “right” way, a single platform, or an industry—I focused on the problem and worked toward a solution.

That mindset built resilience—but more importantly, it built adaptability. I learned how to move with change instead of resisting it. As technology evolved, I evolved with it, not by chasing every new tool, but by staying focused on the work itself and adjusting as the landscape shifted.

The Evolutions I’ve Lived Through

Over the decades, technical advancements has been less about tools and more about shifts in thinking.

Mainframes taught us scale. PCs put computing power on desks. The internet connected everything. Cloud and SaaS untethered work from location. Each era expanded access and capability, even when the tools were clunky, expensive, or hard to adopt.

What mattered wasn’t that desktop publishing, e-commerce, or ERP systems “won.” It’s that they changed who could participate and how work was understood. Desktop publishing shifted who could publish. E-commerce reshaped commerce itself. ERP systems forced organizations to see their own processes clearly—often for the first time.

The value was never just the technology. It was how each shift changed the way we thought about work, systems, and what was possible.

It also created entirely new professional paths—business analysts, systems analysts, product managers, and technology-focused project managers. Roles that expanded who could participate in technology conversations and helped bridge the gap between ideas, people, and execution.

Why This Moment Feels Different

What excites me now isn’t a single breakthrough.

It’s the convergence.

Automation, AI, and no-code platforms aren’t replacing what came before. They’re standing on decades of infrastructure, lessons learned, and hard-earned experience.

For the first time, non-technical people can move from idea to working solution without asking permission. Not because the technology got simpler. Because it finally got usable.

The cost of experimentation has collapsed.

Before, trying something new required commitment—budgets, teams, long timelines. You had to believe (and invest) before you could test.

Now, you can explore first.

You can map a process visually instead of writing a 40-page document. You can test an automation in days, not months. You can prototype before you name the solution. You can learn by doing, not guessing.

That’s not convenience. That’s a structural shift.

Requirements, Reimagined

For most of my career, requirements gathering meant documenting an existing process in exhaustive detail.

Weeks of interviews. Endless flowcharts. Documents meant to freeze how work was done at a moment in time.

That approach made sense when change was expensive and mistakes were unforgiving. You had to define everything upfront because you wouldn’t get many chances to adjust.

Requirements still matter. But they show up very differently now.

They’re no longer static documents. They’re real-time conversations.

Instead of capturing 100 percent of a process before anything gets built, you can explore 10 percent, test it, and see what actually happens.

You build to learn. You adjust based on real use. Insight comes from interaction, not paperwork.

What used to take months of documentation can now happen through short cycles of build, observe, and refine.

This doesn’t eliminate good thinking. It accelerates it.

Why I’m Incredibly Excited

After decades of designing, implementing, and advising, I can see what this unlocks.

Founders don’t have to translate their ideas through layers of technical interpretation. Operators can improve how work flows without waiting in line. Small businesses can experiment the way only large enterprises once could.

The best solutions I’ve seen rarely came from perfect plans. They came from learning in motion. Until now, that kind of learning was risky and expensive.

Today, it’s accessible.

That’s evolution.

The Constant Still Matters

Clarity still beats tools. Understanding the problem still comes first. Judgment still creates the most value.

The difference is that now clarity can be tested instead of debated.

You don’t need to over-document before you begin. You don’t need to freeze the future in a binder. You can think, try, observe, and improve.

A Moment for Discernment

And with every technology shift, there’s also a caution worth naming.

Every major shift brings a wave of instant experts—people who learned a new tool over the weekend and are teaching it by Monday. A quick YouTube video on the latest model or platform can be useful. It can spark ideas. It can lower the barrier to entry.

But it can also oversimplify what is actually complex and can be deflating when trying what should have been “easy”.

Tools like AI carry real risk and real impact—on data, privacy, decision-making, and trust. When guidance skips context, tradeoffs, and consequences, the cost shows up later in places people didn’t anticipate.

Technology doesn’t exist in a vacuum. What we automate, what we amplify, and what we delegate to systems all have downstream effects. Experience still matters. Judgment still matters. Understanding how systems behave over time matters.

Learn from many voices. Experiment freely. But be thoughtful about whose advice you follow and what assumptions come with it.

The goal isn’t to move fast at all costs. It’s to move with intention.

Today I turn 59.

I’m still optimistic. I always have been. But this moment has me genuinely excited about what’s possible.

For the builders who’ve been told to wait. For the founders who’ve been told it’s too complex. For the people who know the work best and can finally shape the tools themselves.

You don’t need a full tech team to begin.

You need clarity, curiosity, and the willingness to try.

Technology doesn’t create “meaning”. But it can help “meaning” travel.

And that is absolutely worth celebrating.

Ready to leverage technology?

If you’re sitting with an idea and wondering what’s actually possible right now, I offer a 15-minute “quick questions” conversation on my website. It’s a space to think out loud, pressure-test assumptions, and decide what’s worth trying next—without overcommitting or overengineering.

No prep. No pitch. Just a focused conversation grounded in experience.

Sign up today.

If this piece resonated, you’re welcome to subscribe. I write for founders and leaders who want to use technology with intention, clarity, and care.

Credit to Dharmesh Shah for You (with AI power) from this youtube video.

They don’t arrive with certainty or clarity. They don’t announce themselves as turning points. I only recognize them later, when I can clearly see life as before and after.

This has happened hundreds of times in my life.

Because I am a faith-full woman, I have language for those moments now. I call them God nudges. Quiet invitations to move differently. To loosen my grip. To trust something I couldn’t yet see. Looking back, I can say they were always in my best interest, even when they felt uncomfortable or inconvenient at the time.

One of those moments happened on April 15, 2025.

That was the day I started turning my phone off for most of the day so I could get my work done. I also switched the screen to grayscale. It sounds small. It wasn’t.

What I began to see almost immediately was how much of my environment I had been welcoming in without question. News. Alerts. National events that were genuinely frightening. A constant stream of input that left me anxious, distracted, and overwhelmed.

At the time, the world felt scary enough that part of me just wanted to hide under the covers. But that wasn’t an option. Since getting sober, my primary purpose has been to be of maximum use to my fellows. And I know this deeply now: I cannot be of maximum use to anyone if I am depleted, dysregulated, or constantly bracing myself for the next headline.

My needs had to become a priority. Not out of selfishness, but out of responsibility.

Around that same time, the idea of committing to 90 days landed differently for me because of the 12-step rooms. There’s a saying there: 90 meetings in 90 days.

Anyone who’s spent time in those rooms knows it’s not about the count.

Two meetings in one day doesn’t replace showing up tomorrow. What matters is the repetition. The daily decision to show up. The slow, steady reshaping of identity into someone who follows through.

That’s what clicked.

This wasn’t about productivity. It wasn’t about discipline for discipline’s sake. It was about becoming someone I could trust. Especially in the quiet moments, when no one is watching. Especially when I’m alone with my thoughts and faced with choices that either move me forward or keep me stuck.

So I made a simple commitment. I reduced noise. I protected my attention. I showed up for the work that mattered. Not perfectly. But consistently.

At the time, I didn’t label April 15 as a turning point. I just made a few small changes that felt necessary. Only now can I see that something shifted internally. I became less reactive. Less scattered. More grounded. More honest with myself.

That internal shift has led me right here, right now. Writing on Substack. Preparing to completely delete my Facebook profile and let go of a decade of posts and “memories.”

There is grief in that. Those posts captured real versions of me. But I no longer believe I need to carry every chapter forward to honor it.

April 15 didn’t feel dramatic. It didn’t feel brave. It felt necessary.

What I’ve noticed in hindsight:

Before: I let my environment set the tone for my day.
After: I choose what gets access to my attention.

Before: I believed staying informed meant staying connected.
After: I understand that constant input was pulling me away from my purpose.

Before: I thought being available was part of being useful.
After: I know I’m most useful when I protect my energy.

Before: I relied on motivation and urgency to move me forward.
After: I trust repetition, daily commitment, and quiet follow-through.

Before: I tried to manage my life from the outside in.
After: I live from an internal alignment I can finally feel and trust.

And looking back, I can see it clearly now.

That was a turn (aka god nudge).

I have no agenda or a plan for writing here, just that since early covid days, writing has been a helpful action for me and since I’m deleting fb and it doesn’t seem to be appropriate for LinkedIn … here we are.

Forever grateful for my bonus life.