Spend enough time reading or watching material about AI and you can come away with a disturbing picture of the future. Jobs may change or disappear. A photograph, a voice, or an article can be convincing without being authentic. As AI systems become more capable, questions about who controls them and how their decisions affect people become harder to ignore. Depending on what you've encountered, you may have wondered whether this technology is opening doors or putting your future at risk.

You may agree with some of those concerns. I take them seriously, too. There are real questions about the work people do, the information we rely on, and the consequences of giving increasingly capable systems responsibilities they may not carry out reliably. Some of the frightening claims we encounter are predictions about a future nobody can describe with certainty. Others concern problems people are already trying to address. We do ourselves no favors by treating them all as either inevitable or imaginary.

There Is Another Question Worth Asking

There is another question I've been returning to: Why are there so many articles, videos, and posts about fearing the future because of AI? I plan to explore that in a separate article. If that question interests you, you can join my newsletter to receive it when I share it. For now, I would like to stay with the question in this headline, because there is a part of the AI conversation that deserves room beside the concerns: What might you be able to create with it?

What Have You Been Hoping to Create?

Perhaps there's an idea you've carried for years. It could be a business, a book, a place where people gather, or a project that would make a difference in the lives of a few people close to you. You may be able to describe what draws you toward it, even if you cannot yet explain how to bring it into the world. Then the practical questions begin. What would it cost? Which skills would it require? Who could help? How would you even know where to start?

A project can matter deeply and still remain untouched because you cannot see a workable path. You may have already looked for help, received an estimate you could not act on, or assumed that learning everything involved would take years. I have experienced some of that distance between an idea and a way to begin. My experience building ARC is one reason I now approach that distance differently.

What Happened When I Started Building ARC

ARC is the system I'm developing to help people discover and build lives aligned with their own Vision. I began with an idea of the experience I hoped people could have through it, but the implementation looked substantial. At one point I received estimates of approximately $16,000 for a minimum viable site and more than $100,000 for a complete implementation, along with a proposed development timeline of roughly six months. Those were estimates for my project, not a universal price for building a site. Still, they gave me a concrete picture of the resources I expected to require before I could put much of the system into use.

When I started working with AI, I could examine parts of the project that had previously seemed to sit behind that large estimate. I explored how different systems might connect, developed architecture, considered implementation options, and began testing parts of the work. A question about one component often exposed another question I had not yet considered. Sometimes an answer revealed a problem with my original approach, so I could examine it before continuing. I was learning about the project while I was developing it, rather than waiting for every part of a complete implementation plan to be settled first.

I moved from concepts into live testing substantially sooner than I had anticipated. The complete ARC platform has not been built or launched, and I would not present it as a finished example of what AI can deliver. What changed was my ability to work on meaningful pieces of a complicated project, investigate how they fit together, and discover what remained unresolved. An idea that had appeared to require one enormous leap could now be explored through a series of actual decisions and tests.

The Discovery Was Bigger Than Speed

It would be easy to tell that story as a time-saving story. Faster progress certainly mattered to me, but the questions I could now examine were changing my view of the project itself. Each part I explored revealed another possibility for how the system might work or how I might approach building it. I began to recognize that I could do more of this work than I had previously considered practical. Then I encountered a similar discovery in a different part of my life.

I developed a four-week rolling production workflow for my articles and related content. A new Cycle enters the workflow every week, so different Cycles move through different stages at the same time. During one particular week, I was doing the work associated with all four weeks of that workflow across different Cycles. I wrote 12 articles that week while also carrying out the applicable social development, image work, assembly, scheduling, and other production responsibilities for the Cycles moving through the pipeline.

The article count is easy to notice, but it misses what that week showed me. I was operating an interconnected production process, making decisions in one stage while other Cycles moved through their own stages. I could see which pieces supported one another and what I could actually sustain while keeping the work moving. It was a very different experience from merely asking AI to produce a stack of articles. I had evidence from my own work that a larger creative operation was becoming practical for me.

I've been working toward replacing my employment income. As I explored what I could build through ARC and what I could operate through the content workflow, I began recognizing commercial possibilities for my storytelling system. Those business ideas were mine. AI did not propose an expanded business portfolio or create my Vision. The experience helped me recognize more ways I might express that Vision through ARC, my personal brand, local newsletters, ghostwriting, and other endeavors. I'm now restructuring the repository where I preserve and organize my work to support that broader scope.

Looking back on those experiences, the contribution that stands out is discovery. The ARC work changed what I recognized as practical to build. The rolling workflow changed what I recognized as practical to operate. The commercial possibilities came into view as I learned what those capabilities might allow me to do. Speed helped, of course, but it was the discoveries along the way that changed how I approached what came next.

AI Can Help Explore, But It Does Not Decide for Me

None of that means AI decides where I'm going. It can suggest an approach, identify a question worth investigating, or help develop a possible route. I decide which direction to pursue and whether a suggestion serves my Vision. If an answer sounds certain but does not hold up when I examine it, I challenge it. If a proposed direction takes me away from what I'm building, I leave it behind. The availability of a useful tool has not transferred responsibility for my decisions to that tool.

I've also had to change the way I work around its limitations. Earlier difficulties with chat continuity and memory contributed to my decision to preserve a durable repository outside ChatGPT. More recent usage limits have encouraged me to be deliberate about what I bring into an AI session. These are practical constraints, and I adjust the process around them. I can make use of what AI offers while continuing to examine its answers, its limits, and the role I choose to give it in my work.

Your idea may have nothing to do with software or publishing. It may be something small enough to begin in an afternoon or large enough that you have no idea where the first step lies. You can start before you have a full plan. Consider why this idea keeps drawing your attention and what you hope the people who experience it might receive. If those questions are still unclear, they are worth exploring in their own right. AI may help you investigate them, compare possible approaches, or discover a question you have not yet asked.

You can also spend time with people who are already using AI to develop ideas of their own. Seeing someone work through a real problem, including the parts where the tool gets something wrong, can teach you more about its usefulness than a sweeping promise about the future. You can decide which applications are appropriate for your circumstances, which information deserves verification, and whether a particular next step serves what you're creating.

The Frightening Picture Is Not the Whole Story

So, is AI really as bad as some say, or is it even worse? Some of the risks are serious, and my experience cannot settle their wider consequences. But that frightening picture is incomplete as an answer to what AI may mean for your life. I have found that it can also help me investigate ideas that once seemed out of reach and recognize possibilities I could not previously see how to pursue. You may discover useful possibilities of your own, or decide that a particular use of AI is not appropriate for you. Either way, the question deserves more than a frightening prediction made on your behalf.

If there's an idea that keeps returning to you, begin with the part you can explore now. You do not have to commit to the whole path before asking the first useful question. And if you'd enjoy working alongside others as you explore, my Friday coworking sessions are open to everyone who subscribes to my newsletter. Bring the idea as it is. We can each work on the part of the road we can see.