There are no items in your cart
Add More
Add More
| Item Details | Price | ||
|---|---|---|---|
The Idea Machine (Article 6 of 8) - The person with a hundred ideas and an urgent need to share all of themOnce upon a time, there was a meeting that actually intended to stick to its agenda. The objective of the meeting was to review the Q3 metrics and align priorities.
Then Kabir had an idea. Actually, seven ideas. Fifteen minutes into the meeting, the team was discussing whether they should launch a podcast, enter a new market, redesign onboarding, and explore an entirely different business model. Every idea Kabir shared was genuinely interesting. The catch? They were all thought experiments. Surprisingly, nobody had looked at the Q3 metrics yet.
Kabir wasn't doing this on purpose. He was genuinely excited, and every idea he raised had merit. The problem was that there were seven of them; they all arrived at once, and the team had come prepared to make one decision, not juggle seven new possibilities simultaneously. The agenda would have to wait. Again. In fact, this meeting had already been rescheduled once for exactly the same reason.
Welcome to The Office Humans. Meet our Idea Machine, Kabir.
The Idea Machine is one of the most energizing and (on certain Mondays) one of the most exhausting people on a team. They are creative, curious and genuinely invested in their own growth, the team's and the organization's. They do not arrive at work wondering what to think about. They arrive with ideas that are already mid-thought, usually about something nobody else has even considered yet.
Here is what this workplace human archetype typically looks like:
Don’t mistake our Idea Machine as an unfocused professional. Their minds are extremely focused on possibilities. The challenge, for them and for the people around them, is that possibility and priority are not always the same thing.
So, What Does Our Idea Machine Bring to the Team?
Before we get to the challenges (because there are certainly some), it is worth spending time to understand the upside of having an Idea Machine in the team because their contribution is real and significant and often undervalued in cultures that prize execution over exploration.
1. They Keep Teams From Getting Comfortable
Organizations that stop generating new ideas tend to keep improving on what already exists, right up until what already exists becomes irrelevant. The Idea Machine disrupts that comfortable trajectory. They are often the people who question the processes, like 'why do we do it this way?' when everyone else runs on autopilot. That question, irritating as it can be to hear for the fourteenth time, is also the question that occasionally changes a lot of things, for good.
Tanvir was eight months into his product role when during a routine check-in, he casually suggested building a feature set for a user segment nobody had discussed before. His manager's first instinct was to redirect him. Six months later, that user segment was the fastest-growing part of the product. Tanvir had been sitting on the idea for weeks. He had simply been waiting for a moment that felt safe enough to say it out loud.
2. They Raise the Energy in a Room
Ideation is contagious. When the Idea Machine is excited and engaged, they pull other people's thinking upward. Meetings that might otherwise be procedural become generative. Colleagues who had nothing to contribute find themselves contributing.
Kabir's team dreaded their monthly strategy reviews. They were long, structured and predictable that had the same people saying mostly the same things in the same order every time. Then Kabir joined the team and within two meetings, he would build on someone's half-formed point with enough enthusiasm that the person who made it suddenly believed in his own idea more than before. In fact, Kabir's energy made thinking out loud feel worthwhile. His manager noticed that meeting satisfaction scores had gone up. She was not sure how to put "Kabir is in the room" into a process document, but she knew it was a factor.
3. They See Connections Others Miss
The Idea Machine's brain loves to relate things and take inspiration. They read something about new weather forecasting technology and immediately connected it to a customer experience problem that their team has been trying to solve for a long time. They are superbly capable of attending an event in a completely different industry and return with three applications for their own context. This cross-domain thinking is extremely rare and genuinely valuable. Well, it is the same kind of thinking that does not show up in a structured planning process.
Nadia works in the HR department. She attended a design thinking workshop just because it looked interesting and also fits her schedule and came back with a framework to enhance candidate experience that her team adapted into one of their most effective hiring tools. While she had not gone looking for a solution, she had simply been in a place where things were being discussed, and her brain could easily make some connections. Most people need to be prompted to think across domains. For Nadia, it happens automatically in workshops, in conversations or while reading the news over breakfast.
Something worth remembering:
Every product that exists was once someone's random thought. Every process improvement began as an interruption to the way things were. The Idea Machine is not a problem to be managed out of existence. They are a resource to be channelized better.
Ideas that come in volume and without structure, often create an organizational fatigue.
Yes, we agree that the trait which makes the Idea Machine valuable in bursts is precisely what makes them difficult to sustain. It's normal that anyone will get overwhelmed in too many directions.
When a team is holding seven new directions at once, deciding on any one of them becomes harder. Each idea competes with the others. Before the team has finished evaluating the first, someone asks, "but what about Kabir's other suggestion?" Nothing gets decided, because every decision feels like closing the door on something that might have been the right answer.
Riya manages a team of six. After a few months of working with Sahil, a natural Idea Machine, she did an audit of their meeting notes. The team had forty-three open ideas, but none formally decided upon; twelve raised more than once, three raised more than five times. The team was busy, engaged, and going nowhere in particular. They were not making decisions. They were just collecting ideas.
Every new idea that enters the system needs someone to hold, remember, evaluate and decide what to do with it. That is cognitive work and it is not free.
When ideas arrive faster than a team can process them, execution goes for a toss. People spend more energy managing the idea backlog than actually building them. Our Idea Machine feels productive by generating so many ideas, but the team gets tired.
By the time Arjun's team finished their Tuesday standup, they had three new ideas from Kabir to consider, two of which had already spawned follow-up questions in the team's chat channel. Nobody had started the actual work yet and more than half of the day is already over.
By the time the team is ready to seriously discuss an idea from two weeks ago, the Idea Machine is already three new ideas ahead and some of them are even contradicting the first idea. When the team finally highlights the contradiction, they get a genuinely well-meaning response, "Oh, I've actually moved on from that one. But yes, worth exploring."
This may look like fickleness, but the fact is this is how their mind works. For the team trying to match this level of expectation where they have a moving target, can be very exhausting.
Priya spent a weekend preparing a detailed brief on a product direction Sahil had proposed in Monday's meeting. On Tuesday, Sahil walked-in with a different direction that he was more excited about. While Priya's brief was thorough and well-researched but now it is irrelevant. Though Priya did not say anything, she did not prepare the briefs anymore.
Ideation Energy vs. Execution Energy
To work well with the Idea Machine and to build a team that can keep up with them, there is one distinction worth understanding clearly.
Ideation energy and execution energy are not the same thing. Most people have some of both. Our Idea Machine has one in abundance and a complicated relationship with the other.
Ideation energy is expansive. It runs on open questions, novelty and the feeling that anything could be the answer. The Idea Machine in this mode is energized by making connections, seeing possibilities and pulling threads that nobody else noticed. Aisha, another Idea Machine, describes it as "thinking in widescreen." She is aware that not everyone experiences meetings this way and she finds this mildly baffling.
Execution energy works differently. It narrows and commits. It tolerates the less glamorous work of following through on something that was exciting three weeks ago and is now just a task on a list. Where ideation opens doors, execution closes them deliberately and in a much more systematic way.
For the Idea Machine, the execution energy is not impossible, but it is simply less natural for them. Imagining the thing is way more engaging than building it. And most importantly, it must look like an individual’s cognitive style, not a flaw.
Why Teams Need Both and Why They Rarely Have Them in Balance?
The most effective teams have a healthy distribution of both kinds of energy. Too much ideation without execution produces a very creative, very busy team that never completes anything. Too much execution without ideation produces a very productive team that gradually runs out of ideas worth growing.
But balance is rarely the natural state of a team. Ask me why. Because managers hire people who think like them, work like them and communicate like them. An Idea Machine in a leadership role will often build a team of other Idea Machines. An execution-oriented leader builds a team of executors. The imbalance is less of an accidental type and more of a reflection of what the person at the top finds comfortable and familiar.
The Idea Machine, without a counterbalance, tilts the team toward the first problem. The solution is not to reduce their ideation energy, but to create structures that channel it into execution without diminishing it.
For our readers who manage a team that includes our Idea Machine
Think of the Idea Machine's output in two categories - fuel and sparks. Fuel is the idea that, if pursued, would genuinely move something important forward. Spark is an idea that is interesting but not relevant right now. Your job is not to eliminate the spark because it will always be there. Your job is to build a system that separates the two without making the Idea Machine feel like their thinking is unwelcome.
How to Funnel Ideas Productively
Throughout the read, do keep the goal in mind. The goal is not to slow the Idea Machine down. It is to give their ideas a place to land with a structure that honours the thinking without letting them or the team get overwhelmed with the execution.
For Managers
For the Idea Machine Themselves
If you recognize yourself in this archetype and you probably do, because the Idea Machine is often highly self-aware about the fact that they have a lot of ideas, even if the impact on others is less visible; here are some practices worth building.
How Does The Idea Parking Lot Work?
The Idea Parking Lot is a shared team practice that gives ideas a place to exist without demanding immediate attention. It is most effective when the Idea Machine takes ownership of it, without feeling like it’s administrative work. It also acts as a support for idea machines to build the prioritization muscle that does not come naturally to them. The manager's role is to establish it as a team norm and ensure it is reviewed consistently.
It sounds almost too straightforward to be useful. Teams that use it consistently find that it is one of the highest-leverage things they do. Let’s understand how it works.
The parking lot solves three problems simultaneously. For the Idea Machine, it provides assurance that their idea has been captured and will be seen, which removes the urgency to raise it immediately and repeatedly. For the team, it creates a single location for ideas rather than a sprawl across meeting notes, Slack threads, and email chains. And for the manager, it creates a regular rhythm for idea evaluation that is low-cost and high signal.
Basically, the Idea Machine's greatest risk is not running out of ideas. It is that their best ideas never find the structure they need to become real. And the team's greatest risk is not being overwhelmed by ideas. It is dismissing the remarkable one because it arrived in the same sentence as six others.
So, to wrap this up, we have a prompt for you to reflect on...
Think of the last idea you had that really excited you. What happened to it? Was it shared, captured, evaluated, or did it join the long list of things you were going to get back to?
And what would it take to give your best ideas a fighting chance?
Let us know in the comments below.

Ishita Mukherjee