I'm 75 years old.
Over the course of my life, I've accumulated a considerable amount of experience. I've worked in manufacturing, technology, operations, and management. I've solved problems, managed people, made mistakes, and learned that things rarely work out exactly as planned.
At 75, I have something else: the freedom to pursue an idea simply because I think it might help someone.
Over the past several months, I've developed three working applications and a website that brings them together under an initiative I call Better Life Makers.
None of the ideas was revolutionary. Two grew out of earlier efforts that hadn't succeeded. The third evolved from an activity I've enjoyed for years.
I didn't undertake extensive market research, prepare financial projections, or develop elaborate business plans.
I simply thought that if I could create something that helped a few people live better lives, the effort would be worthwhile.
Along the way, I discovered a new way to apply a lifetime of experience to solving problems. Artificial intelligence played an important role, but not necessarily the one people might expect.
The most important part of the process wasn't getting answers from AI.
It was learning how to ask better questions.
The first question is rarely the right one
Throughout my working life, I've believed that a large part of solving any problem is asking the right questions.
But there's a complication.
Often, you don't know enough about a problem to ask the right question when you begin.
You start with what you know. You ask a question, consider the answer, and learn something. That new knowledge allows you to ask a better question.
Sometimes the answer confirms your original thinking. Sometimes it shows that you were approaching the problem incorrectly. And sometimes it reveals possibilities you hadn't imagined.
That's the process I've used in developing my projects.
I didn't start with detailed technical specifications. I started with problems, frustrations, and ideas.
Marilyn Speaks: An idea that began with failure
My first project, Marilyn Speaks, began with an attempt to create a simple communication tool on my own.
The idea was straightforward: nine large buttons on a screen, each speaking a phrase when pressed.
Communication boards aren't new. I wasn't inventing a new concept. I simply wanted something inexpensive, easy to use, and adaptable to an individual's needs.
My initial attempt failed.
I didn't have the programming skills to accomplish what I wanted, and hiring someone to develop the application would have required an investment that was difficult to justify.
Later, I began exploring the idea through conversations with AI.
Could we create a screen with nine buttons?
Could each button speak a different phrase?
Could a caregiver change those phrases without knowing anything about programming?
Could the application run on an inexpensive Amazon Fire tablet?
Could sets of phrases be saved, transferred, and restored?
Could the application speak different languages?
And more recently, could someone record a familiar voice instead of relying on computer-generated speech?
Each question led to an answer, which often led to another question.
Today, Marilyn Speaks is a working application with capabilities I hadn't envisioned when I began.
But those capabilities weren't the result of a comprehensive plan developed at the outset.
They emerged from an ongoing process of questioning, experimenting, testing, and refining.
The important point is that I didn't need to know what was technically possible before I began asking.
Saving Memories Forever: Revisiting an idea that hadn't succeeded
Saving Memories Forever was an earlier project intended to preserve people's voices and personal stories for future generations.
The original effort didn't succeed as I had hoped.
But I continued to believe the underlying idea had value.
Why shouldn't a grandchild be able to hear a grandparent tell a bedtime story years after that grandparent is gone?
Why shouldn't families preserve someone's favorite joke, a funny memory, or a personal message?
When I revisited the project, I began questioning some of my original assumptions.
Perhaps asking someone to record their life story was too ambitious.
What if we made the first step much smaller?
Instead of recording an entire life, why not start with a bedtime story?
Or a joke?
Or a memory that takes only a few minutes to tell?
Then came questions about making recordings easy to save and share.
Could a recording be sent to a family member through a simple private link?
Could the recipient listen without installing an application or creating an account?
Could that link expire automatically after seven days?
The resulting application is simpler and more approachable than my original vision.
And that may be its greatest strength.
Sometimes the most important question isn't what more we can do. It's what we can eliminate to make something genuinely useful.
My Folk Circle: An idea that evolved rather than arrived
My third project, My Folk Circle, developed differently.
For years, I've participated in a small folk singing group. We get together, share what's happening in our lives, choose songs, and sing.
Over time, I've come to appreciate that the sharing and companionship are at least as important as the music.
I began wondering whether other people, particularly older adults, might enjoy something similar.
Could technology make it easier for someone to organize a folk circle?
Could a group enjoy familiar songs without needing a skilled musician to lead them?
Could an application display lyrics, play recordings, and guide people through a gathering?
Could people add their own music?
The idea evolved through repeated conversations and experiments.
We developed ways to organize songs, display lyrics, manage recordings, and move from one participant to another.
Then I began asking whether we had made the application too complicated.
What would someone actually need to lead a small group?
Eventually, the process became remarkably simple:
Share. Choose. Sing. Pass.
Someone shares a little about themselves, chooses a song, the group enjoys it, and the next person takes a turn.
My Folk Circle continues to evolve because I'm still learning what works and what doesn't.
And that is part of the enjoyment.
Why I didn't begin with a business plan
During my working years, I was accustomed to evaluating projects in terms of costs, benefits, markets, and financial returns.
Those considerations are important when substantial resources are at risk.
But the economics of experimentation have changed.
With today's technology, I can explore an idea, develop a prototype, test it, and make improvements at remarkably little financial expense.
My principal investment is time.
That changes how I decide whether something is worth pursuing.
I don't have to demonstrate that thousands of people will purchase an application before deciding to develop it.
If an application helps a few people communicate, preserve family memories, or enjoy companionship, that may be sufficient justification.
Could some of these projects eventually become commercially viable?
Possibly.
I would welcome the opportunity for organizations with the appropriate expertise and resources to develop some of them further and bring them to a larger audience.
But commercial success wasn't the reason I started.
I wanted to see whether I could create something useful.
When the cost of trying an idea becomes very small, the possibility of helping someone can be reason enough to try.
The computer didn't always get it right
I don't want to give the impression that developing these applications was simply a matter of asking AI to create something and accepting the result.
Far from it.
A feature might work on my computer but fail on an inexpensive tablet.
A screen might look fine in portrait orientation but become unusable in landscape.
A button might disappear behind an on-screen keyboard.
A recording might not play correctly.
A seemingly minor improvement could interfere with something that had worked perfectly the day before.
These problems produced another series of questions.
Why doesn't this work?
Is the problem the device, the browser, or the application?
Can we correct it without changing anything else?
Is there a simpler approach?
How can we test whether the correction actually works?
I didn't need to understand every line of programming code. I needed to understand what the application was supposed to accomplish, recognize when it wasn't doing so, and describe the problem clearly enough to guide another attempt.
That is a different skill from programming, but it is still problem-solving.
And it's a skill I've spent a lifetime developing.
A useful tool is not necessarily an unqualified good
I don't want my experience to be interpreted as an endorsement of artificial intelligence or everything it may bring to society.
I have serious questions about its broader consequences.
Technologies that give individuals remarkable new capabilities can also displace workers, spread misinformation, undermine privacy, and concentrate power in ways that may not benefit society.
My experience doesn't resolve those concerns.
What I can say is that, in these particular projects, AI gave me access to technical capabilities that would otherwise have been difficult or expensive to obtain.
But the technology didn't identify the problems I wanted to solve.
It didn't decide what would make someone's life better.
And it didn't determine which solutions were worth pursuing.
Those decisions came from my own experience, values, and judgment.
I've spent a lifetime asking questions, evaluating alternatives, and learning from what works and what doesn't. That process isn't new, and it certainly wasn't invented by AI.
What changed was the cost and speed of experimentation.
I could explore an idea, test it, discover its shortcomings, and try something different without making a substantial financial commitment.
That opened possibilities for me. Whether the broader impact of AI on society will ultimately be positive is a much larger and more complicated question.
I don't pretend to know the answer.
I do know that the ability to ask thoughtful questions, challenge answers, and exercise independent judgment is becoming more important, not less.
At 75, experience is an asset
One of the most interesting aspects of this process is how much I bring to it.
I have a lifetime of experience recognizing problems, evaluating alternatives, understanding people, and distinguishing between something that sounds good and something that might actually work.
I don't know how to write the software that powers these applications.
But I know what I want them to accomplish.
I can recognize when a proposed solution is unnecessarily complicated.
I can question whether a feature will confuse someone.
I can test an application, recognize when it isn't working, and describe the problem.
And I can draw on decades of experience to decide whether an answer makes sense.
The technology supplies capabilities I don't possess.
I supply judgment, context, curiosity, and an understanding of the people I hope to help.
Neither is a substitute for the other.
Learning is its own reward
There is another dimension to this experience that has become increasingly important to me.
At 75, I am very aware that physical aging brings limitations.
There are things I can't do as easily as I once did. That is simply part of growing older.
But intellectually, I don't feel that I have to stop growing.
In fact, learning new things has become one of the activities I value most.
Every time I discover a new capability, understand a technical concept, or solve a problem that seemed beyond my reach, I have a sense of accomplishment.
I'm gaining something.
And that feeling is especially satisfying at a time in life when it's easy to focus on what we are losing.
I've learned about how web applications work, how information is stored, how audio can be managed, and how small design decisions affect whether someone can actually use a product.
I don't need to become an expert in all these subjects.
I enjoy understanding enough to ask the next question.
The learning itself has become part of the reward.
Helping others has become its own reward
As I've gotten older, I've also found that what gives me the greatest satisfaction has changed.
Earlier in life, professional accomplishments, business results, and financial success were important measures of achievement.
Today, I find much more joy in the possibility that something I do might make another person's life a little better.
If Marilyn Speaks helps someone communicate a need or express a thought, that matters.
If Saving Memories Forever preserves a grandparent's voice for a grandchild, that matters.
If My Folk Circle helps a few people who might otherwise be isolated spend an enjoyable hour together, that matters.
None of these accomplishments requires a large market, substantial revenue, or public recognition.
The satisfaction comes from knowing that the effort was worthwhile to someone.
That is what Better Life Makers is about.
Creating something is only the beginning
I've also come to appreciate that developing an application and getting it into the hands of people who might benefit from it are very different challenges.
I can create something that works, but that doesn't mean I have the expertise, resources, or desire to market it, maintain it, and develop it indefinitely.
Those activities require different skills and commitments.
Some of my projects may be better served by finding organizations that can take them further.
Others, like My Folk Circle, may remain personal efforts that I can enjoy sharing with people directly.
I'm still exploring those possibilities.
The objective isn't necessarily to build an organization or a business around every idea.
It's to find a way for a useful idea to continue being useful.
That may mean someone else eventually carries it forward.
And that, too, begins with asking questions.
The questions are just beginning
I started this journey with a few ordinary ideas, some previous disappointments, and a willingness to experiment.
I didn't know exactly what was possible.
I certainly didn't anticipate developing three applications.
What made it possible wasn't suddenly acquiring the skills of a software engineer.
It was discovering that I could combine the experience I already had with technical knowledge and capabilities that had previously been difficult for me to access.
I would ask a question.
Consider the answer.
Challenge it.
Try something.
Learn from the result.
And ask another question.
The process continues today.
At 75, I don't know how many more projects I'll undertake or what will become of the ones I've already developed.
But I do know that I want to keep learning, exploring, and finding ways to help others.
Growing older may limit some of the things we can do physically, but it doesn't have to limit our curiosity, our creativity, or our ability to contribute.
I've spent a lifetime learning that 50% of the solution is asking the right questions.
At 75, I'm still discovering better questions to ask.