The Problem With Keeping Creative People Interested
Wes Towers runs Uplift 360, a business focused on website design, development, and SEO. His team had spent years building websites in WordPress, following established systems and processes.
That consistency was good for the business—but Wes noticed that one of his team leaders was becoming bored.
The employee was an advanced programmer who had been with the company for a long time, and Wes could see that the repetitive nature of the work was no longer challenging him.
Then an unusual opportunity appeared: a complex dating website unlike anything Wes or his team had built before.
Wes saw an opportunity to give his team leader something new and interesting to work on. The employee loved the idea.
There was just one problem Wes couldn’t see yet.
The Employee Who Was Supposed to Solve the Problem
The employee wasn’t merely interested in the project. He became the person responsible for figuring out how to build it.
He handled the proposal. He scoped the project. He understood the technical requirements.
And he was essentially the only person on the team who knew how to do it.
Wes submitted the proposal, won the project—and then, a couple of weeks later, the employee quit.
Suddenly, Wes was responsible for delivering a project that his team had never done before, using technology and processes he didn’t know how to build himself.
He managed to hire some additional help, but much of the work fell back on him. He spent long hours doing the technical grunt work himself.
Eventually, they delivered the website, and the client loved it.
The client had no idea how much pain and effort had gone into getting it across the finish line.
The Risk Wes Didn’t See
The experience taught Wes an important lesson about key-person risk.
His normal business model had systems, processes, repetition, and multiple people who could work within the same structure. This project was different. It depended heavily on one person with specialized knowledge.
But there was another layer to the problem.
Wes hadn’t taken on the project because it was strategically important to the business. He had taken it on partly because he wanted to give a valued employee something interesting to do.
The concession worked—at least temporarily.
The employee was excited about the project.
Then he left anyway.
Wes later recognized that he probably should have realized the employee was already exploring other opportunities. But at the time, he simply wanted to give someone he valued a more interesting challenge.
Sometimes the Solution Isn’t More Money
The conversation then moved into a broader question: why do employees leave even when their employers try to make things better?
Morgan shared a pattern he’d noticed in his own experience managing companies. Employees would sometimes ask for raises, receive them, and then leave within a few months anyway.
His interpretation was that people can sometimes mistake the source of their dissatisfaction. They may assume money is the problem when the underlying issue is that they’re bored, frustrated, disengaged, or simply ready for something different.
That brought the conversation back to Wes’s original problem.
If creative employees need more stimulation, simply giving them more money may not address the reason they’re unhappy.
Creating opportunities to experiment, solve unusual problems, and explore new ideas might.
Turning Boredom Into Experimentation
One of the ideas discussed was Google’s well-known 20% approach: giving employees some time to work on projects outside their normal responsibilities.
Wes immediately connected the idea to the current changes happening in his industry, particularly the opportunities created by AI.
Rather than forcing employees to spend all their time following established processes, businesses can create room for talented people to experiment.
That doesn’t necessarily mean taking on an entirely unfamiliar client project and making one person responsible for it.
It could mean giving the team a problem and letting them figure out a creative solution.
A New AI Problem Becomes a Business Idea
That idea led to a long tangent about a problem Wes’s team was currently facing.
They had won a WordPress project for an Australian company whose international websites were built using different proprietary software. Because they couldn’t access the original system directly, the team would have to manually transfer hundreds of products—including text, images, PDFs, and pricing information—into the Australian site.
Wes wondered whether AI could automate much of that process.
Morgan encouraged him to give the team the problem rather than the solution: explain what needs to happen and let the people closest to the technology figure out how to accomplish it.
That could potentially turn a one-off internal solution into something much bigger, such as a WordPress plugin.
The important part wasn’t necessarily the specific idea. It was the method: give smart people interesting problems to solve and let them use their expertise.
What Wes Would Do Differently
Looking back, Wes realized there was another opportunity hidden inside the original project.
By the time they finished the dating website, they had learned how to build a type of site they had never built before. They had developed knowledge, solved technical problems, and created something that had a market.
Instead of abandoning that capability completely, Wes could have considered turning it into a new area of the business.
But by then, he was exhausted.
After spending months getting the project across the finish line largely without the employee who had originally driven it, Wes didn’t want to see the project again.
That exhaustion mattered.
Business Owners Burn Out Too
One of the more important lessons from the story was that burnout isn’t limited to employees.
Wes had taken on a complicated project, lost the person who knew how to build it, hired additional help, and personally absorbed much of the work required to finish it.
By the end, he was ready to move on.
That emotional state can affect business decisions just as much as it affects employee decisions. Even when there may be a good business opportunity sitting inside a difficult project, sometimes you’re simply too burned out to pursue it.
For Wes, the lesson wasn’t just about managing employees or avoiding unfamiliar projects. It was also about recognizing the limits of the person running the business.
Creating a Path for People to Stay
The conversation eventually returned to the original question: how do you keep talented, ambitious people engaged?
One possibility they discussed was creating a path toward partnership or ownership.
Traditional professional-services businesses often had a clear progression: someone joined early in their career, moved through increasingly senior positions, and eventually became a partner.
In a modern employee structure, that path often doesn’t exist.
For someone ambitious, there may eventually be nowhere else to go inside the organization.
Wes had seen the partnership model work firsthand in an accounting practice and recognized how powerful it could be when people become genuinely invested in the organization.
The Horror Story That Turned Into a Coaching Session
Wes’s original horror story was relatively simple: he gave a talented employee a challenging project to keep him engaged, the employee quit shortly afterward, and Wes was left to finish the project himself.
But the conversation uncovered much more.
It raised questions about key-person risk, employee motivation, creative freedom, money versus engagement, burnout, delegation, experimentation, and long-term career paths.
And by the end of the episode, Wes wasn’t just looking back at what had gone wrong.
He had several new ideas to take back to his team.