When I started writing here, I made you a promise in a single line: the genius is already in your building, and the work is letting it show up. Over these first posts I have tried to show you what that work actually looks like, in the places it usually hides.

We started with the quarter-million-dollar retreat that changed nothing, and the hard truth underneath it: knowledge is not capability, and capability that never gets integrated into the daily work simply evaporates. We looked at the four questions every employee is silently asking, and how each unanswered one pulls a little more of a person back into reserve. We sat with the uncomfortable fact that the employee we have written off as not caring is usually someone who ran into a wall we built, and then went quiet. We met three supervisors, the Overwhelmed, the Clueless, and the Experienced-But-Stuck, and admitted we have been all three.

Then we widened out. We watched a firm try to include its people with a training program and miss the real work of integrating them into how decisions get made. We watched a brilliant, proven model for children die because the structure around it was built for silos. We saw the once-a-year performance number that teaches people their growth is an afterthought. And we followed an avoided conversation all the way to a hundred-and-sixty-thousand-dollar bill.

Different stories, different corners of the work. But if you stand back, they are all the same story.

In every one of them, the capability was already there. The diverse young professionals, the interdisciplinary trainees, the employee with the late reports, the supervisor who never got honest feedback, the quietly excellent person nobody was developing. None of them were short on genius. In every case, something in how the organization operated kept that genius from reaching the work: a program standing in for a practice, a structure built for silos, a ritual standing in for a relationship, a silence standing in for a conversation. That is suppression. And the antidote, in all of it, is the same. Integration. The deliberate, daily, often uncomfortable work of weaving each person’s full capability into how the work actually gets done.

That is the whole idea behind this newsletter, and it is why I will keep coming at it from every angle. Supervision. Difference. Structure. Performance. Conflict. Coaching. They look like separate management topics. They are not. They are all the same craft, the one almost nobody is trained for: releasing the capability your organization already has, and already pays for.

If you want the fuller argument, with the framework underneath it, that is what my book, The Genius We Suppress, is for. And if your organization wants help doing this work in practice rather than reading about it, that is what my daughter Karen and I do at Cascone Consulting. But you do not need either to start. You need only to look at the people around you with a different question in mind.

So I will leave you where we began, with the practice rather than the theory. Tomorrow, pick one person. Ask yourself, honestly, what part of them your organization is currently leaving outside the room, and what one thing you could change to let it in. Not a program. Not a form. One real act of integration. Then watch what comes back.

The genius is already in your building. It always was. The work, the only work that ever actually mattered, is letting it show up. I am glad you are here for it. Let’s keep going.

John

The Director of Operations at a small manufacturing company called me about one of his supervisors. She ran shipping, receiving, and inventory, with six people reporting to her, and she was known throughout the company as a hard nut. She ran her department by strict discipline and a short fuse, and she had the highest turnover of any department in the building.

The Director had tried to coach her. Every time he raised her management style, she pushed back the same way: this is what it takes to protect the company’s assets and hit our deadlines. And she had a trump card. She had been there since the beginning, and the founder, now president and CEO, liked her. “I have been doing this for twenty years,” she told him, “with no complaints from the president.” The CEO did, in fact, praise her now and then for running a tight ship.

So the Director did the thing that felt safest. Nothing. He did not press the conflict with her, and he did not raise his concerns with the president, because he knew about that long relationship and did not want to step into it. He kept telling himself he would deal with it later. He kicked the can down the road.

The can stopped rolling when a routine disagreement over a procedure blew up between the supervisor and one of her staff. She fired the employee on the spot. The employee filed a wrongful termination suit. The company lost and paid out a year’s salary plus compensatory damages. The supervisor, the untouchable one, eventually resigned anyway. The Director avoided the conversation he should have had, the one he kept postponing because it was uncomfortable. And it cost the company one hundred and sixty thousand dollars, a lawsuit, and a long line of good people who had quit her department over the years that nobody ever added to the bill.

We tend to think of avoiding conflict as the kind, professional, mature thing to do. Keep the peace. Do not make waves. But avoided-conflict is not peace keeping. It is suppression with better manners. The Director was not protecting the company by staying quiet. He was protecting his own comfort, and the cost of that comfort compounded silently in the background until it all came due at once.

Here is the thing about a workplace conflict worth having. It is almost always a place where two real perspectives are colliding, and the better way forward lives somewhere in the friction between them. Integrating those perspectives, actually putting them in the same room and working the disagreement until something better comes out, is hard and uncomfortable, and it is precisely the work that has to be done. When you avoid it, you do not make the collision go away. You postpone it, and you guarantee that when it finally happens, it happens at the worst possible time and in the most expensive possible way. The fear, real or imagined, associated with leveraging power, as the supervisor did, to protect unacceptable behavior always has consequences and none of them are good.

The genius of both the supervisor and her staff got suppressed in that silence. She never got the honest feedback that might have helped her change, because the one person positioned to give it decided it was not worth the discomfort and risk. Her people never got a workplace they could survive. And the organization paid for that suppression later, with interest.

So here is the discipline. Think of the one conversation you are currently avoiding: the difficult high performer, the protected veteran, the peer whose work is slipping. Now ask yourself honestly what it is costing you to not have it, not in comfort, but in turnover, in resentment, in risk quietly accumulating where you cannot see it. Avoidance always feels cheaper than the conversation. It almost never is. The bill just arrives later, and larger, and with someone else’s name on the lawsuit.

The Director was not a coward. He was a decent man who did the very human thing of choosing the small comfort in front of him over the large discomfort he could not yet see the cost of. Most of us do it. The conversation we are dreading sits there, costing a little more every week we leave it alone, and we tell ourselves we will get to it. The supervisors I admire most are not the ones who engage conflict. They are the ones who have learned that the conversation they are avoiding is usually the most important work on their desk, and that the longer they wait, the more it costs the people they are responsible for growing.

A confession to open: I have read, scored, and signed more performance appraisal forms than I can count, and I have never once seen a number on one of them change a person for the better.

You know the form. Eight or ten categories down the page: job knowledge, quality, productivity, communication, dependability, initiative, teamwork. Under each, a few indicators, and beside each indicator a scale from one, poor, to five, exceeds expectations. Add it up, plot the total on a line from below acceptable to exceptional, tack on a box for strengths and weaknesses and an improvement plan, collect two signatures, and file it. Once a year, usually on the employee’s anniversary date, the ritual repeats.

Now ask what that number actually told the employee. It did not tell them how the rating connected to their real work. It did not tell them what specifically to improve, or why. It said nothing about where their career might go inside the company, nothing about which behaviors to keep and which to change, nothing about what to aim for in the year ahead. It was a score, not a conversation.

So it is no surprise that most employees see the exercise for what it is. They understand it serves the company, not them. They know it exists mainly to justify compensation decisions. And they know that the moment it is signed, it goes in a drawer and is not mentioned again until a month before next year’s review. The form is impeccable. The substance is absent.

Here is the shift I have spent years helping managers make. Performance management is not an event you hold once a year. It is the ongoing work of integrating a person’s growth into the work itself, so that getting better at the job and doing the job become the same activity. That sounds abstract, so let me give you the protocol I actually hand to new supervisors.

Start by knowing your people, not their numbers. Your job is to make them better at what they are there to do, and you cannot stretch someone you do not understand. Learn their aspirations, their expectations of themselves, their real strengths and the places they struggle.

For them to trust you with that, they have to know you too: what you expect, and how you intend to supervise them. Trust is the foundation of the whole relationship, and trust is built through engagement that is continuous, not episodic. One conversation a year is the definition of episodic.

Build their development into the work assignments themselves, not alongside them. Growth is not a separate program. It is what happens when you and the employee treat the work as a shared project aimed at two outcomes at once: better results for the company and a more capable person.

Then keep a real cadence. Regular check-ins, frequent enough to actually see progress and adjust. Make their ownership of the work explicit, and ask for their input often enough that they know it is a real value to you. And keep looking for the next place their capability can grow, inside the company if you can, and honestly beyond it if you cannot.

You do not need to wait for HR to redesign the form. The form was never the thing. Pick one person and replace one piece of the ritual with one real conversation: not a score, but an honest exchange about what they are working toward and what would help them get there. Then have another one a few weeks later. The number measures the past. The conversation builds the person.

The cruelest thing about the once-a-year number is not that it is useless. It is that it teaches your most capable people that their growth is an afterthought, reviewed on a schedule set by the calendar rather than by the work. People give their best to the places that take their becoming better at their job seriously. A score in a drawer has never once told someone they were taken seriously. A standing conversation does, every time it happens.

Some years ago, I had the good fortune to work on a government initiative that I still consider one of the best ideas I have ever seen put into practice. The goal was to find alternatives to institutional care for children with developmental disabilities. The insight behind it was simple and powerful: these children were being treated by doctors, psychologists, teachers, physical and occupational therapists, speech therapists, and other specialists who were all trained in separate worlds and rarely worked as one.

So this governmental initiative built a place where they would. Seventeen universities, training professionals across eleven different disciplines, sent their students to a Center for Interdisciplinary Internships. There, the trainees did hands-on treatment of real children, working in close coordination across disciplines to build something none of their separate programs taught: a holistic, integrated approach to children with developmental challenges that affected performance in all areas of their life.

It worked. It worked beautifully. The children’s performance improved across every area. The trainees developed competencies they could never have gained inside their own university silos. By any honest measure the integrated model was a clear success, and everyone involved could see it.

The whole point, the real objective, was for that interdisciplinary competency to flow back and influence universities’ curriculum, to become part of how each discipline trained its specialists from then on. That was the prize. Prove it at the Center, then build it into formal training everywhere.

It never happened.

The siloed structure of each profession’s training was so deeply built into the curriculum that there was simply no room for interdisciplinary competency-building. It was never made a priority. The disciplines went on training the way they always had. The Center kept doing excellent work on its own, helping the children it served, but the larger vision, the one that would have changed the interdisciplinary planning and development of these children, quietly died. The Center itself eventually closed, undone by the usual combination: shifting political support and the sheer durability of silo thinking.

I have carried that one with me for a long time, because it taught me something no amount of good intention can get around. Structure is not neutral. An organization’s structure either integrates people’s contributions or it fragments them, and when it fragments them it will defeat even a proven, successful, demonstrably better way of working. The Center did not fail on the merits. It failed because the structure around it was built for silos, and a structure built for silos will reject an integrated model the way a body rejects a transplant.

This is what leaders miss when they try to release their people’s capability one supervisor, one pep talk, one training, one reorganization at a time. You can have the best intentions and the most talented people, and if the structure routes the work into silos, forces it through too many approval layers, or splits a whole job across boxes on a chart that never talk to each other, the capability has nowhere to go. The org chart is not just a picture of who reports to whom. It is a set of decisions about whose contribution reaches the work and whose gets stranded.

So if you lead at any scale above a single team, this is the question worth sitting with. Take one important piece of work in your organization and trace it across the structure. How many handoffs does it survive? How many boxes does it cross before anyone is actually allowed to integrate the pieces? Every one of those boundaries is a place where someone’s creative genius is asked to stop at a line on a chart. The most capable person in the world cannot integrate what the structure keeps apart.

I still think about those children, and about the trainees who, for one bright stretch, got to practice their professions the way they were always meant to be practiced, as part of a whole. For a while, the genius in that building was fully integrated, and you could see the difference in the children’s lives. It did not last, not because anyone stopped believing in it, but because the structure around it never made room for it. The saddest waste is not the idea that fails. It is the idea that works, and dies anyway, because nothing was built to hold it.

A professional services firm I worked with had quietly become a different company than the one it started as. Twenty-five years earlier its professionals were almost all white, male, and post-graduate trained. By the time I arrived, the staff was largely multiracial, female, and young, college-educated and ambitious. The talent in the building had changed completely. How the firm operated had not.

The board noticed and asked the CEO to do something about it. The CEO handed the assignment to his senior management team: build us a diversity, equity, and inclusion plan. The team was a dozen executives and department heads, most of whom had been with the firm fifteen years or more.

Almost immediately they split into three camps. One group was genuinely excited and wanted to build something ambitious. A second rolled its eyes, certain this was a recycled compliance exercise and another round of political correctness to work through. A third did not object but honestly could not see how any of it would help the firm do better work.

They met weekly for months. The three camps never moved. The conversations got tenser, then wearier, until the team did what exhausted committees do. They recommended a series of DEI training programs for the staff and called it done. Everyone left the room unsatisfied. The CEO reported to the board that the firm had launched a DEI initiative. The training rolled out over six months, and then it was forgotten. No policy changed. No practice changed. What did change was palpable and measurable in the worst way: more frustration among employees, lower productivity, and higher turnover among exactly the young, diverse talent the effort was supposed to engage.

Here is what went wrong, and it is not what you might think. The team did not fail because its members were biased, lazy or disinterested. It failed because it treated inclusion as a program to deliver rather than a practice to build. Training is a form. It is something you can schedule, attend, and check off. The substance, the actual work, was never on the table.

Real inclusion is not an event. It is integration, and it runs in two directions. There is vertical integration: making sure people at every level are engaged and own the work they are asked to perform for the firm. All employees, not just the senior or tenured ones, are genuinely part of how information moves through the organization and where decisions get made. And there is horizontal integration: making sure different people and different work groups are actually woven together, their perspectives are openly shared and engaged where the work happens. A firm whose talent has become diverse but whose decisions, structures, and daily habits still run the way they did twenty-five years ago has not substantively included anyone. It has diversified the roster while leaving the game plan unchanged.

That is what the management team missed. The young, multiracial, female professionals were not asking for a training session. They were the firm’s future capability, and they could see plainly that nothing about how the place actually operated had engaged or energized them. A workshop does not fix that. Integrating their judgment into how work gets assigned, how decisions get made, and how careers get built does.

So if your organization is wrestling with this, here is the question that cuts through it. Set the program aside for a moment and ask: in the last year, has the way we actually make decisions and do the work changed to reflect and tap the capabilities of the people who are now doing it? If the only thing that changed is that people attended a special learning event, you bought the form of inclusion and skipped the substance. The diverse talent you worked so hard to hire is still standing outside the room.

I think about that team sometimes, and about the talented young people who left in the year after the firm’s big initiative. They did not leave because the training was bad. They left because they had been told, in the most expensive and well-documented way possible, that the firm had looked hard at whether they truly belonged in determining how the work got done and decided the answer could wait. People feel that decision long before anyone says it out loud. And they do not wait around forever to be integrated into a place that has decided it can include them later.

Most suppression of talent does not come from villains. It comes from decent people who are overwhelmed, or unaware, or stuck in habits that used to work for them. I have met hundreds of supervisors, and the ones doing damage almost never know it. Over the years I have come to see three types. I have been all three myself at different points in my career, which is the only reason I can describe them without judgment.

The first is the Overwhelmed.

Sarah ran a customer service team of eight. Smart, and she cared, but every time we met she looked like she was drowning. “I know I should be developing my people,” she told me. “Having career conversations, giving regular feedback. But I can barely keep up with the daily fires. By the time I get through everything urgent, I’m too exhausted to think about what’s important.”

The Overwhelmed are not failing because they do not care. They are buried under tactical work and unclear priorities, with a constant sense that they are not good enough at the job. Their people’s genius goes unused not by decision but by exhaustion. There is nothing left at the end of the day to use it. The Overwhelmed do not need more training. They need a system, and they need to understand they are not broken. They are operating without a framework that releases their full capabilities.

The second is the Clueless.

Tom was a department director with terrible retention. Three people had quit in two months. He was genuinely baffled. “I give them all the freedom they want,” he said. “I don’t micromanage. Isn’t that good management?”

I spent two hours with his remaining team. Tom had not given them freedom. He had given them neglect. He hired capable professionals and then disappeared. No feedback, no direction, no sense of what mattered. When people asked for help, he told them to figure it out. When they made mistakes, he said nothing until the annual review, where a year of small errors suddenly appeared at once. Tom was not a bad man. He truly believed that leaving people alone was respect for their competence. He had no idea his team experienced it as abandonment. The Clueless do not need education. They need awakening, and that usually requires someone making the consequences of his assumptions impossible to ignore.

The third is the Experienced-But-Stuck.

Jennifer had supervised her accounting team for fifteen years. She knew her job, had built the systems, earned the respect, and kept her retention solid. Until she didn’t. In one year, two of her best people left and the rest seemed to fade. Her team described feeling stuck in amber: everything worked the way it always had, but the world had changed and Jennifer’s approach had not.

She knew it. “I know the old ways aren’t working as well,” she admitted. “But these habits worked for fifteen years. They feel safe. And honestly, I’m not sure the new approaches will work as well.” The Experienced-But-Stuck already have the insight. They do not need to be told the problem. They need help turning what they already know into different daily habits, and honest feedback on whether the new habits are working.

Three types, one truth they all share. None of these supervisors set out to waste the capabilities of their people. Sarah was too tired, Tom was too unaware, Jennifer was too comfortable. The talent on their teams did not vanish. It went unused, for three different reasons that all felt reasonable to each supervisor.

So, the useful question is not “am I a good boss or a bad one.” It is narrower and more honest: on my worst week, which of these three am I? Name it, and you have done the hard part, because the type is fixable once you can see it. The danger is never the type. The danger is not knowing which one you are.

There is a sentence I have heard from supervisors more than any other, usually said with a tired shrug. “They just don’t care anymore.”

It is almost always wrong. Not because people never lose motivation, but because motivation is the least common reason for poor performance, and it is the first one we reach for. It is the easiest explanation, because it puts the problem entirely inside the employee and lets everyone else off the hook.

Let me show you how the real story usually goes.

A manager tells me an employee’s monthly reports keep coming in late. He has already alerted me that he may have drawn his conclusion about the problem: poor time management, maybe a motivation problem. The corrective action plan is to document it, discuss it with the employee and if improvement does not happen, put it in her review.

So I met with the employee and asked some questions. It turns out the data she needs to write the report arrives late from another team, every cycle. By the time she has it, she has lost most of her window. She has asked that team to prioritize her requests, but they are buried too, and she has not escalated it because she did not want to start a fight across departments.

The late reports were never a time management problem. They were a system problem, sitting one desk upstream, completely outside her control. But the form of the failure, a late report with her name on it, pointed straight at her. So she was about to be blamed, in writing, for something she did not cause and could not fix alone.

This is the pattern I want you to see, because it is everywhere once you start looking. An organization mismanages a person’s work. It hands them unclear priorities, or starves them of what they need, or buries them, or never tells them what good looks like. The person’s performance suffers, exactly as you would predict. And then the very supervisor whose system caused the problem reads the result as proof the person was never that capable to begin with.

The genius gets mismanaged, and the employee gets the blame.

I do not say this to make supervisors feel guilty. Most of the time there is no bad intent anywhere in the work processing chain. The manager receiving the late reports was not cruel. He was busy, and “she needs to manage her time better” is a faster solution than “let me trace this back to its source.” That is exactly why the mistake is so common. The honest explanation takes more work than the convenient one.

But the convenient one has a cost, and the person who pays it is usually your most capable employee. The one with enough talent that you expected more, and enough self-respect that being blamed for someone else’s bottleneck is the thing that finally makes them leave.

So here is the discipline I would ask you to practice. The next time you catch yourself deciding that someone has stopped caring, treat that conclusion as the last possible explanation, not the first. Before you reach a judgement, walk the problem upstream. Ask what they need that they are not getting. Ask what is happening one desk over. Ask what you might have set up, without meaning to, that makes good work harder than it should be.

Most of the time, you will find that the genius did not disappear. It ran into something, hit a wall the person did not build, and then went quiet. Your job is not to judge the silence. It is to find the wall.

The conference room looked like every corporate training I had ever walked into. Twenty-two senior executives and managers in comfortable chairs, notebooks open, coffee steaming. Outside the windows of an expensive resort, palm trees moved in the breeze. Inside, a well-known organization development firm was running day three of a five-day management retreat.

The insurance company hosting it had spared nothing. Five full days. Case studies, simulations, self-assessments, recreation scheduled neatly between sessions. The agenda promised to transform these leaders: better performance management, readiness for rapid growth, stronger succession planning, higher organizational capability. The bill came to two hundred and fifty thousand dollars for twenty-two people.

At the end of the week the evaluations came back glowing. Every participant said they had learned a great deal. The facilitators were praised. By every measure anyone bothered to take, the week was a triumph.

I checked back a year later.

Not one objective had been met. No change in behavior. No improvement in management performance. No improvement in retention. Nothing. The quarter million might as well have gone into the resort pool.

Here is what still bothers me about it. Everyone involved believed they had succeeded. The firm delivered excellent content. The participants genuinely learned useful ideas. Leadership saw happy faces and positive forms and checked the box marked “management development.” Nobody lied. Nobody failed at their assigned task. And the whole thing accomplished none of what it was built to do.

My doctoral advisor had a name for this. I once gave him an elaborate answer about the greatest challenge facing managers of complex organizations, something about resources and strategy. He smiled and said, “Battling the tyranny of form over substance.”

The form was flawless. Prestigious firm, full agenda, glowing reviews, satisfied people. The substance, the actual change in how those managers led once they got home, never arrived. Because no training program, however good, can create change by itself. Training does not change people. Worksheets do not build capability. Knowledge without implementation is expensive entertainment.

This is the same trap that suppresses genius inside an organization every single day, only quieter and easier to ignore. We confuse the form of a thing with its substance. We confuse hiring a capable person with using their capability. We confuse a title and a job description with actually integrating that person into how the work gets done. The form is in place, so we assume the substance is too. Then we wonder why the capability we paid for never shows up in the results.

Capability that is not integrated into the daily work evaporates. The brilliant idea in the training binder, the talent listed on the org chart, the potential noted in the performance review: all of it is form. None of it does anything until it is built into how the work actually happens, and kept there, and supported.

That is the difference this newsletter is about. Not the form of good management, which is easy to buy and easy to display. The substance of it, which is harder, slower, and the only thing that ever actually works.

So before your organization spends its next quarter million on a beautifully run event, ask the one question that will still matter a year later: what, specifically, will be different in how the work gets done on the Monday after everyone goes home? If there is no answer, you are buying form. The substance, and the genius it would have released, stays in the binder.

There is a genius walking out your door every evening that no one ever asked to fully show up.

I don’t mean the obvious stars. I mean the quiet ones. The analyst who sees the flaw in the plan three weeks before it fails and says nothing, because the last two times she spoke up it cost her. The warehouse lead who could redesign the whole workflow but was hired “to move boxes,” so he moves boxes. The new hire who arrived full of ideas and learned, by month four, to wait to be told.

None of those people are short on capability. Their organizations are short on the practice of using it.

For forty plus years I’ve studied a single, stubborn pattern. A company hires a person for their full intelligence, judgment, and creativity, then builds a job, a structure, and a set of unwritten rules that quietly let only a fraction of it through. The capability doesn’t vanish. It just stops showing up. And then we call the person disengaged, or average, or “not a culture fit,” as if the narrowing were their own idea.

I’ve watched this in 150-person companies and in 32,000-person corporations. For-profit, nonprofit, government, at home and abroad. The pattern holds. The genius is almost always already in the building. What’s missing is the work of letting it out.

I’ve come to call that work integration.

Integration is the opposite of suppression. Suppression is what happens by default, usually with no ill intent at all, when a busy supervisor or a controlling structure or a box-checking process narrows a person down to a task. Integration is the deliberate practice of weaving each person’s full capability into how the work actually gets done. Not as a slogan on a wall, but as the daily craft of supervising people, building structures that invite contribution instead of fragmenting it, and handling performance, difference, and conflict in ways that bring people more fully in rather than shrinking them down.

Here is the part that took me too long to accept. The suppression is rarely the employee’s fault, and its cost is rarely charged to the person who caused it. A supervisor narrows someone’s role, ignores their ideas, manages them by fear or by neglect, and then, when that person goes quiet and careful and small, reads the result as proof the person was never much to begin with. The genius got mismanaged, and the employee got blamed for the damage.

That is the crisis underneath the crisis everyone talks about. Yes, your best people leave. But before they leave, they stay and shrink. The resignation is just the last and most visible thing that a suppressed genius does.

So this newsletter is about the other path.

I’m going to write about what I’ve actually watched work and fail across four plus decades, in plain language, from real situations. Some days I’ll hand you a principle you can use on Monday morning. Some days I’ll tell you a story that lands harder than any principle would. I’ll write across the whole range of where this plays out: how you supervise, how you integrate genuinely different people instead of flattening them into sameness, how the org chart itself either releases capability or strangles it, how performance and conflict get handled, and how leaders coach the people beneath them.

It’s all one practice wearing different clothes. The leader’s real job, the one almost no one is trained for, is to release the capability they already paid for.

If you supervise even one person, this is for you. If you run a function or a company, it’s for you at a larger scale, because structure suppresses genius far more efficiently than any single bad boss ever could. And if you are the person whose genius is currently walking out the door each night unasked, I hope this gives you language for what you’ve been feeling, and maybe a little leverage to change it.

I’ll meet you here regularly. Subscribe and come along.

The genius is already in your building. The work is letting it show up.

John

Thank you for being here.

For decades I worked inside organizations watching supervisors succeed and fail, and asking as precisely as I could what made the difference. What I found is that every employee carries genius, and most workplaces never release it. The best leaders do. This newsletter is where I share what I have learned about how.

The regular writing begins Monday, August 3rd, and will arrive three mornings a week. Stories from the field, the ideas underneath them, and practical ways to lead so the people on your team do their best work.

If you supervise people, I think there is something here for you. Subscribe below so the first piece reaches you when it publishes, and I am glad you found your way here early.

Dr. John A. Cascone

Your best employee is interviewing you. Quietly, continuously, without ever scheduling a meeting. Every day they are gathering evidence about whether this is a place where they can do their best work or a place where they should start looking elsewhere.

After many years of watching people stay and watching people leave, I have come to believe the interview comes down to four questions. Your employees may never say them out loud. They may not even put them into words for themselves. But they are answering them all the time, and the answers decide whether their full capability shows up or quietly withdraws.

Here are the four.

One. What am I responsible for, and did I have any say in shaping it? People own what they help build. When someone has had real input into their goals, they are invested in reaching them. When goals are simply handed down, people comply, but they do not commit, and compliance is a fraction of what they are capable of.

Two. Am I getting better at my work, and does anyone notice or care? People need to grow, and they need their growth to be seen. A person who is improving and feels invisible will eventually stop improving. A person who is stuck and ignored will eventually leave, often long after they have mentally checked out.

Three. Can I succeed here without burning out? Capability runs on a sustainable system, not on heroics. When every week is a crisis and good work depends on staying late and absorbing the overflow, your best people do the math. They can succeed or they can survive, but not both. So they leave, or they quietly lower their effort to a level they can sustain, which looks like disengagement but is really self-protection.

Four. Where am I going, and is this place helping me get there? People want a direction, and they want to believe their current work moves them toward it. When someone cannot see how today connects to their future, they start looking for a future somewhere else, no matter how much they like the present.

Four questions. Notice what they have in common. Not one of them is about pay. Not one is about perks or ping-pong tables or the mission statement on the wall. They are about whether the work itself lets a person bring their whole self to it and become more in the process.

When all four answers are yes, people stay, and more than that, their genius shows up. When even one answer turns to no, you are at risk, and the risk is not only that they leave. The bigger cost comes first, in the months or years they stay while contributing a shrinking share of what they could.

Here is what to do with this. Pick one person on your team. Not the one who is struggling. The one who is quietly excellent and easy to take for granted. Ask yourself, honestly, how they would answer those four questions today. Not how you hope they would. How they actually would, based on what you have done and not done in the last month.

If you are not sure of an answer, that uncertainty is the assignment. You do not have to fix all four at once. You have to start asking, because the employee already is.