Igniting Change: How to Innovate Without Leaving Your Job

Before You Begin: The Fundamental Trade-Off

Before the first chapter, it helps to see the bargain plainly. An intrapreneur and an entrepreneur both create new value, but they make very different trades to do it. Neither is better; they suit different people at different moments in life.

Capital source. The intrapreneur uses the company’s budget, tools, data, and people. The entrepreneur uses savings, loans, or investors.

Risk. The intrapreneur risks time, reputation, and standing at work, while the company carries the financial loss. The entrepreneur risks their own money and livelihood and carries the loss.

Autonomy. The intrapreneur’s is limited: you need sponsors, permission, and approvals. The entrepreneur’s is high: you decide, within the law and your cash.

Financial reward. For the intrapreneur, usually a salary, sometimes a bonus or promotion. For the entrepreneur, uncapped profit, or nothing at all.

Speed to market. The intrapreneur is slower to start but able to scale fast on the company’s reach. The entrepreneur is fast to start but slow to scale on limited resources.

Who keeps the value you create. For the intrapreneur, the company, unless it chooses to share. For the entrepreneur, you, along with the losses.

The last row was added from the author’s own story, which opens Chapter 1. Read it with that row in mind.

Chapter 1: Mastering Corporate Diplomacy and Influence

An idea wins support inside a company only when leaders can see their own priorities in it. This chapter shows how to anchor an idea to strategy, build a working coalition, and pitch it so an executive can say yes to a first step.

Anchor Case: Fourteen Days at Minimum Wage

Gene A Constant at JCPenney, Springfield, Illinois, 1972 to about 1977

In 1972 I was fresh out of the Navy, where I had been a radioman. I believed those skills would carry over into civilian life. They did not. Nobody in Springfield needed a radioman. I used my GI Bill benefits to enroll in computer programming school, back when you programmed a computer by plugging wires into a board and fed it data on punch cards. I was washing dishes to get by, and I was quickly learning that programming was not for me.

A kind man at the school knew the personnel manager at the Springfield JCPenney. It was not an ordinary store. JCPenney called it a “developmental” store, a place to try new ideas, and it even had its own grocery department and gasoline station. My friend walked me in to meet the personnel manager, who searched hard for something I could do. I had never worked in a big store. I had never sold anything. I did not own a real camera; my only camera had been a five-dollar Kodak Instamatic I bought from a kid. My only “photo experience” was a card certifying that I could run a 16-millimeter movie projector.

It happened that the camera department’s salesman was leaving for his two weeks of Army Reserve training. The store needed a warm body behind the counter. Out of plain kindness, they gave me that spot: fourteen days at minimum wage, and that was supposed to be the end of it.

I was painfully shy. I could barely say my own name out loud. But I spent those fourteen days learning everything I could. When a camera manufacturer’s sales representative came through on his annual visit, I asked whether he could spare some time to teach me, and he gave me more than an hour. By the time the salesman came back from the Army, management had decided I knew more than he did. He was moved to the radio department. I was given the camera department, permanently.

What Nobody Asked Me to Do

The department was dirty and disorganized. Nobody had cleaned the inside of the glass counters in a long time.

So, without asking anyone, I found a bucket of soapy water and some rags and got down on my hands and knees. I emptied one counter at a time, cleaned it thoroughly, reset the shelves, and put the products back by category and by price, with the most expensive items on the top shelf where customers could see them. I had never organized a store before. I simply had a sense of how it should look. That has been true my whole life: I often just know what needs to be done, and I could not tell you where the knowledge came from.

Then I kept going. I learned to take inventory in the locked stockroom. I learned what retail calls “shrinkage,” the merchandise that disappears and cannot be explained. Before long I was doing the buying, setting prices, marking things down and deciding what to sell. On paper, a department manager oversaw several departments, including mine. In practice, his own manager, a man named Gene, gave me those responsibilities and let me run the camera department almost any way I saw fit.

The store let me check out display cameras and take them home, so that I could learn to use what I was selling; on minimum wage, I could not afford to buy them. Manufacturers’ representatives stayed after work to teach me about their products, often for hours, glad that a store as big as JCPenney cared about their line. Every year I paid my own way to the photography convention in Chicago to learn from people in other stores.

The Ideas, One at a Time

Each idea was a small risk, and each one opened the door to the next.

The advertising. One day I walked into the store’s advertising department on my own and asked to see the camera ads being prepared. The advertising manager knew little about photography and was glad for the help, so he made my changes. Soon the store let me lay out all of the camera advertising. Then I learned that camera manufacturers set aside a percentage of their sales as advertising money for stores like ours, money that went to JCPenney’s home office in New York. Within a few years, the home office gave me control of that money for my department, and I used it to buy and promote the products the manufacturers were most eager to see sold.

Meet the Manufacturer. With that budget, I invited every manufacturer’s representative who wanted to take part to stand at my counter during a department-wide camera sale, so customers could ask the experts directly. My first attempt drew a few people. The second went very well, and it became an event we held twice a year.

Free camera repairs. A repairman who ran his business out of his home came by hoping I would send him customers. I visited his workshop, and then I invited him to do free repairs in my store, as long as the fix was simple enough to do on the spot. The first time, a few people came. Word of mouth did the rest, and it became one of the busiest days we had.

Free classes. After hours, I taught customers what I was learning about photography. A local television station broadcast my offer of free camera classes as a public service announcement, which was free advertising for the store. I also became a Boy Scout merit badge counselor in photography.

The tourist photo contest. With the State Journal-Register, I created a summer contest that sent tourists and residents to photograph Springfield landmarks. I asked the managers of each site, including the State Capitol and Abraham Lincoln’s Home, for permission to put up large wooden signs, and every one of them agreed. Yashica donated the grand prize camera, and the newspaper published the winners each week.

The State Fair. I became assistant superintendent of the Illinois State Fair’s photography promotion, and superintendent the following year. I also talked the store into entering a float in the fair’s parade: a beach scene on a donated 40-foot trailer, with fake palm trees from our display department and cashiers who volunteered to ride along and hand out candy, holding signs that said “Buy Kodak film from JCPenney.” Our store manager helped me shovel the sand onto the trailer himself. As far as anyone at the company could tell me, no other JCPenney store had ever entered a fair parade. The float won a Governor’s trophy, which the store, of course, kept.

The pegboard test. The most valuable space in any store is next to the cash registers, where people buy on impulse. Film was expensive then, around four dollars a package, so the store sold it only from behind the counter, where it could not walk away. I asked for permission to hang Kodak film on the pegboards beside the store’s registers. Management worried that theft would wipe out any gain, so they approved it on one condition: if shrinkage rose, the experiment would end.

It did not end. Film sold at the registers just as well as it sold behind my counter, so film sales roughly doubled, and the inventory counts showed no increase in shrinkage at all.

The Results

By my third year, my department had won a regional contest judged on growth in both sales and profit, beating stores in larger cities, including St. Louis. Then the company told me that my department was one of the top ten camera departments in all of JCPenney. At the time, JCPenney was at its largest: in 1973 it operated 2,053 stores, about 300 of them full-line department stores. The company would not tell me where I ranked within the ten. I have never stopped wishing I knew.

Customers would stand in line to talk to me, even when someone else was standing at the counter with nothing to do.

The One Who Resisted

Not everyone was happy. A woman who had worked my counter for years believed the job should have been hers. I was much younger, and I had no experience. She spent the rest of my time there inventing stories about me and my family. To my face she was polite; other supervisors told me what she said behind my back. I never tried to punish her or have her fired. Management knew what she was doing and did not take her seriously. I believe her campaign said more about her than it ever said about me.

The Bargain

Here is the part of the story most books about innovation leave out.

I wanted one thing from JCPenney: a place in its management training program. I had outperformed every manager in that store, and most of the company. But the program required a college degree. I did not have one. I did not even have a high school diploma; I had never spent a single day in high school. I did everything I could think of to earn an exception.

JCPenney refused. I was never allowed into the program, so I could never be promoted to manager. For all I built, the company paid me little more than minimum wage. In about 1977, I left.

And every idea was a risk I carried myself. I took authority no one had formally given me. I told my bosses what I was going to do rather than asking whether I could. Any one of those ideas could have gone wrong. Someone at the home office could have decided I was out of line. I could have been let go at any point along the way.

So was it worth it? Yes, and I want to be careful to say why.

JCPenney gave me a place to learn. I walked in an ashamed young man with an eighth-grade education and no teeth, washing dishes to get by. I walked out a confident man who knew photography inside and out, who could teach a room full of strangers, speak on television, and earn a second income photographing as many as two weddings a weekend. I came to think of those years as a college degree, with the tuition paid, indirectly, by JCPenney. Most of all, those years taught me who I was: an entrepreneur, even while I was working for someone else.

What This Means for You

Three lessons from my JCPenney years run through every chapter of this book.

1. Earn the room before you ask for it. I never started by asking permission to change the department. I started by cleaning it. Every bigger idea, the advertising, the budget, the pegboards, came after people had seen what I did with the last one.

2. Make every experiment safe to say yes to. The pegboard test worked because I gave management a clear rule for stopping it. When you ask a nervous boss for a yes, hand them the off switch.

3. Know the bargain you are in. An intrapreneur shares risks and rewards with the employer, but the sharing is not always fair. Some companies will let you build value without ever rewarding you for it. Go in with your eyes open. Take the learning, the skills and the confidence, because those are yours to keep, wherever you go next.

The Recognition Trap

Many companies celebrate innovation only after it has obviously paid off: the profitable launch, the industry award. There is nothing wrong with celebrating success. But when success is the only thing ever rewarded, people stop taking uncertain bets, and they stop reporting problems early.

Smart companies reward the behavior that leads to success: a careful experiment, an honest report of failure, an early warning that saved money. The best rewards are often not money at all. They are time set aside for the work, help from people higher up, and the chance to learn across departments. Bonuses tied only to outcomes can even backfire, tempting people to exaggerate results or claim credit for others’ work.

JCPenney, in the story you have just read, rewarded neither the process nor the results. It is the clearest lesson in this book about knowing the bargain you are in.

Strategic Alignment

An innovative idea becomes valuable inside a company only when decision-makers can see how it advances something they already care about. This is the central discipline of strategic alignment. It is not the act of shrinking an ambitious idea until it appears harmless, nor is it a cynical exercise in using executive language to disguise a personal project. It is the work of identifying the genuine intersection between a promising opportunity and the organization’s stated priorities, financial realities, customer commitments, and future direction.

Many intrapreneurs make the same early mistake: they lead with the idea itself.

They say, “We should build an AI-powered customer portal,” or “We need a new sustainability platform,” or “I have a way to redesign the onboarding process.” These may be excellent ideas. But to an executive managing competing budgets, operational risk, regulatory pressure, quarterly targets, and an overloaded workforce, an idea without context can sound like one more demand on an already strained system.

Leaders do not usually reject innovation because they lack imagination. More often, they reject it because the connection to the company’s immediate and long-term agenda has not been made clear enough. Your task is to make that connection unmistakable.

Begin by learning the organization’s declared strategy. This sounds obvious, yet many employees know only the slogans attached to the strategy rather than the operational commitments beneath them. “Customer centricity,” “digital transformation,” “operational excellence,” and “growth” are common corporate phrases. On their own, they are too broad to guide a proposal. You need to understand what they mean in practice.

If the company claims that customer centricity is a strategic priority, ask what measures leaders use to prove it. Is the organization trying to improve retention? Reduce service response times? Increase customer lifetime value? Enter a new market segment? Simplify a difficult purchasing journey? Strategy becomes real when it is connected to choices, investments, metrics, and trade-offs.

Listen carefully in town halls, quarterly earnings calls, leadership meetings, investor presentations, departmental reviews, and internal communications. Pay attention not only to what senior leaders say, but to what they repeat. Repetition is a signal. If executives mention margin improvement in every update, they are likely under pressure to reduce costs or improve productivity. If they repeatedly discuss trust, compliance, or resilience, the company may be responding to external scrutiny or operational vulnerabilities. If they emphasize speed to market, the organization may be losing ground to competitors.

Your innovation should be framed as a response to one of these strategic pressures.

A teaching case: The employee who appears here, and again in every chapter, is a realistic illustration built for this book, not a real person or company. Following one initiative from a first observation to lasting change shows how the ideas in each chapter work together.

Consider an employee who notices that customers routinely abandon the company’s online application process. Her first instinct might be to propose a complete redesign of the digital experience. That may indeed be the eventual solution. But if the company’s current strategy emphasizes profitable growth in underserved customer segments, her proposal becomes much more compelling when framed differently: “We are losing qualified applicants during a process that is especially difficult for the customer group we have identified as our next growth market. A targeted improvement could increase completed applications, reduce support costs, and help us meet the growth objective already set for this year.”

The underlying idea is similar. The strategic meaning is entirely different.

This is the first translation an intrapreneur must master: from feature to business outcome. Executives rarely fund features. They fund outcomes such as revenue growth, cost reduction, risk mitigation, customer retention, faster delivery, improved compliance, stronger employee productivity, or strategic differentiation.

A useful way to test your own thinking is to complete this sentence: “If we do nothing, the company will struggle to achieve its goal of __ because __.” If you cannot fill in both blanks with specificity, your alignment is not yet strong enough.

For example: “If we do nothing, the company will struggle to achieve its goal of reducing service costs because simple customer requests continue to be routed to highly trained specialists.” This statement identifies a strategic goal, a current obstacle, and an implied opportunity. It gives your proposal a business reason to exist.

Strategic alignment also requires an honest understanding of timing. A well-aligned idea introduced at the wrong moment may still fail. A company facing a major integration after an acquisition may not be ready to consider a new platform, however promising it appears. A business unit in the middle of a cost-reduction program may resist an initiative that requires immediate investment, even if it promises future savings. A regulated organization may need legal, security, or compliance review before it can experiment with a customer-facing solution.

Timing does not always mean waiting. Often, it means changing the shape of the proposal.

If leadership is focused on controlling costs, do not begin by asking for a large transformation budget. Propose a small experiment that uses existing tools to test whether a process improvement can reduce rework. If the company is managing a difficult system migration, position your idea as a way to solve a migration-related customer problem rather than as a separate innovation program. If the organization has declared a commitment to responsible growth, show how your initiative can create value without adding unnecessary risk.

This is not compromise in the negative sense. It is intelligent sequencing. Successful intrapreneurs know that the route to a larger vision is often a smaller, strategically timed first step.

To identify the right first step, map your idea against four questions.

First, which corporate priority does this directly support? Name one or two priorities, not six. An idea connected to everything usually appears connected to nothing.

Second, what measurable outcome could it influence? Estimate the possible impact, even if your early numbers are directional. You may not know that a new process will reduce handling time by exactly 18 percent, but you may be able to show how many hours are currently spent on manual work, how often errors occur, or how many customers abandon a journey.

Third, what existing initiative, capability, or investment could this build upon? Alignment becomes much stronger when your proposal leverages work the company has already funded. Perhaps there is an underused data platform, an existing automation license, a customer research program, a new strategic partnership, or a team with relevant expertise. Rather than presenting your innovation as an additional burden, show how it increases the return on assets already in place.

Fourth, what risk does your idea reduce? Intrapreneurs often focus so heavily on opportunity that they overlook the persuasive power of risk reduction. An initiative may reduce the risk of customer churn, data errors, regulatory failure, employee burnout, reputational damage, or competitive displacement. Particularly in established companies, avoiding a meaningful downside can be as compelling as pursuing an upside.

This process turns vague enthusiasm into a strategic case. Instead of saying, “I think we should automate this workflow,” you can say, “This workflow consumes approximately 4,000 hours a quarter, delays customer responses, and creates avoidable errors. A limited automation pilot would support the operational-efficiency target, use technology we already license, and help reduce a known service risk.”

The second statement does not merely ask for attention. It earns attention.

Still, alignment must remain authentic. Executives can sense when someone has attached fashionable strategy language to an unrelated project. If every idea is somehow described as transformational, customer-centric, AI-enabled, sustainable, and growth-oriented, none of those claims will be trusted. The discipline is to identify the real connection, including the limits of that connection.

Sometimes the most strategically aligned conclusion is that your original idea should be changed.

You may discover that the company’s priority is not to acquire more customers but to retain its most profitable ones. In that case, a broad acquisition-focused campaign may need to become a retention tool. You may learn that the organization is not prepared to invest in a new system but has urgent demand for better reporting. Your initial concept might evolve into a data visibility pilot that creates the evidence for a later system investment.

A pivot like this is not a defeat. It is one of the advantages of intrapreneurship. Unlike an external founder who may be committed to a single market thesis, you have access to internal knowledge, existing customers, operating data, and experienced colleagues. Use that access to refine your idea before you ask the organization to commit to it.

The strongest strategic alignment is built through conversation, not assumptions. Speak with people close to the business problem: frontline employees, account managers, operations specialists, finance partners, customer support teams, and analysts. Ask them where strategic goals are being slowed down by friction. Ask what work is expensive, repetitive, vulnerable to error, or frustrating for customers. Ask which leadership priorities feel meaningful at the working level and which have not yet translated into action.

These conversations do more than improve your proposal. They help you discover language that resonates inside the organization. A finance leader may describe the challenge as margin leakage. An operations leader may call it handoff failure. A customer team may describe it as unnecessary effort. Each perspective reveals part of the same problem, and each may become important when you later build support.

Ultimately, strategic alignment is the bridge between personal initiative and organizational permission. Your idea may begin with your observation, your curiosity, and your willingness to act. But it gains momentum when others can see themselves in it: the executive trying to deliver a growth target, the manager trying to improve a broken process, the frontline employee trying to serve customers better, and the company trying to remain relevant in a changing market.

Before you seek sponsorship, budget, or formal approval, be able to state your case in one clear sentence: “This initiative helps the company achieve this priority by solving this specific problem, using this practical approach, with this measurable benefit.”

That sentence is not your full pitch. It is your strategic anchor. Every later conversation, coalition, and presentation will be stronger because it begins there.

Building the Coalition

Once you have established a strategic anchor, the next challenge is organizational: turning a well-aligned idea into a coalition capable of moving it forward.

This is where many promising intrapreneurs become discouraged. They assume that if the business case is strong enough, the organization will naturally support it. In reality, companies do not make decisions as a single, rational entity. They make decisions through people, functions, incentives, histories, competing priorities, and formal authorities. An initiative can be strategically sound and still stall because legal was informed too late, technology sees an unmanageable support burden, finance cannot identify a budget owner, or a middle manager worries that the change will disrupt an already overloaded team.

This is often called internal politics. The phrase can make people uncomfortable because it suggests manipulation, favoritism, or backroom maneuvering. But politics, at its most practical and ethical level, is simply the process through which groups with different interests make collective decisions. You cannot avoid it by refusing to participate. You can only choose whether to navigate it thoughtfully or be surprised by it later.

The intrapreneur’s task is not to “win” against other departments. It is to understand the landscape well enough to build a path that respects legitimate concerns while maintaining momentum toward the opportunity.

Start by identifying the people who can affect your initiative. Some will have the power to approve it. Some will control resources you need. Some will be asked to implement the change. Some may be exposed to risk if the project goes badly. Others may become influential advocates because they experience the problem directly.

A simple stakeholder map is useful here. List the relevant individuals or groups and consider four questions for each: What do they care about? What might they fear? What can they contribute? What authority do they hold?

Take the example of the employee who identified abandonment in the company’s online application process. Her initiative may touch more people than she initially expects. The digital product team may own the application journey. Marketing may care about campaign conversion. Customer support may see the consequences of customer confusion every day. Compliance may be concerned about disclosures and fair treatment. Legal may review new language or data usage. Technology may need to assess integration demands. Finance may want evidence that an improvement in completed applications creates profitable growth rather than merely higher volume.

Each group is looking at the same proposal through a different lens. The digital team may ask, “Can we build this within the roadmap?” Customer support may ask, “Will this actually reduce call volume?” Compliance may ask, “Could a simpler process inadvertently create a regulatory issue?” Finance may ask, “What is the value, and when will it appear?”

An intrapreneur who treats these questions as resistance will create opponents. An intrapreneur who treats them as information will build credibility.

Not every stakeholder requires the same approach. It helps to distinguish among sponsors, champions, contributors, gatekeepers, and skeptics.

A sponsor is a senior person with enough organizational influence to create access, remove barriers, protect the initiative when priorities shift, or secure resources. Sponsors do not need to do the project work themselves. Their value comes from their authority and their willingness to use it.

A champion is someone who genuinely believes in the initiative and speaks positively about it when you are not in the room. Champions can exist at any level. A respected operations manager, an experienced analyst, or a customer service team lead may become more influential than their job title suggests because colleagues trust their judgment.

Contributors provide expertise, capacity, data, or operational knowledge. They may not be emotionally invested in the idea at first, but they can make it more realistic and more effective.

Gatekeepers have a formal responsibility to review, approve, or control a necessary part of the work. Security, procurement, legal, compliance, finance, risk, and technology architecture teams often play this role. Calling them “red tape” may feel satisfying, but it is rarely productive. Their job is to prevent the organization from creating expensive, unsafe, or noncompliant problems. The more you understand their requirements early, the more quickly they can help you find a workable route.

Skeptics are not always enemies. Some are protecting teams that have been burned by poorly designed change in the past. Others have seen similar projects fail. A thoughtful skeptic can reveal weaknesses in your assumptions before they become public failures. The goal is not to convert every skeptic into an enthusiastic supporter. It is to understand whether their concerns are valid, address what you can, and prevent avoidable surprise.

This is why one-on-one conversations matter before formal meetings. Large meetings encourage people to defend their territory, perform certainty, or raise objections for the first time in front of an audience. Individual conversations create space for candor.

Instead of arriving with a finished proposal and asking, “Will you approve this?” begin with a learning posture. You might say, “I am exploring a small way to reduce abandonment in the application process. Your team sees an important part of this journey. Could I get your perspective on where a change might create value or create problems?”

This question accomplishes several things at once. It shows respect for the other person’s expertise. It gives you information you may not possess. It makes the stakeholder more likely to see the initiative as something they helped shape rather than something being imposed upon them.

Listen for the concerns beneath the first objection. If an IT leader says, “We cannot take on another platform,” the real issue may be limited engineering capacity, a history of unsupported tools, security concerns, or frustration with projects that create long-term maintenance without clear ownership. If a finance partner says, “The numbers are not compelling,” the underlying concern may be that your benefits arrive too late, are difficult to measure, or fall outside that team’s budget responsibility.

The answer is rarely to argue harder. It is to adapt the proposal. Perhaps the first experiment can use an existing technology platform, as discussed in the earlier section on strategic alignment. Perhaps the pilot can be limited to one customer segment, with success measured through completed applications, support contacts, and conversion quality. Perhaps you need to identify an operational owner before asking the technology team to commit resources.

This is coalition building in practice: not collecting superficial endorsements, but changing the initiative until the people required for success can responsibly support it.

Reciprocity is an important part of this process. People are more inclined to help those who have demonstrated that they understand and support their work. If you need an operations leader’s assistance, learn what that leader is trying to solve this quarter. If your idea can reduce a handoff failure that burdens their team, make that benefit explicit. If it cannot, be honest about the effort you are asking them to contribute and look for ways to reduce it.

Do not treat colleagues merely as channels to approval. A coalition built on extraction will collapse when work becomes difficult. A coalition built on shared value can survive delays, revisions, and competing demands.

Executive sponsorship should usually come after you have done enough groundwork to make the request credible. Approaching a senior leader too early can create a difficult dynamic. If you have not consulted the functions that will be affected, the executive may ask obvious questions you cannot answer: “Has legal reviewed this?” “Who owns implementation?” “What does technology think?” “How will we measure the result?” An unanswered question can turn an intriguing opportunity into a premature proposal.

This does not mean you need universal agreement before seeking sponsorship. Waiting for complete consensus is another common way innovation dies. Instead, aim for informed support from the people closest to the problem and early awareness from the functions with meaningful veto power. Then approach a sponsor with a clear ask.

For example: “We have identified a high-abandonment point in the online application journey that affects a priority growth segment. Customer support and digital product both see the problem, and compliance has advised on the boundaries for a limited test. We would like sponsorship for a six-week pilot using our existing platform. We will measure completion rates, support contacts, and conversion quality before requesting any broader investment.”

This is far stronger than saying, “I have an idea for improving the application process.”

A good sponsor is not simply the most senior person you can reach. The best sponsor has a meaningful connection to the strategic outcome, enough influence to help, and a reputation for acting on commitments. A senior executive who vaguely likes innovation but has no stake in the problem may offer encouragement without action. A business leader whose targets are directly affected by the opportunity may be more willing to lend political capital.

Coalitions also require careful attention to credit. In established organizations, people are understandably wary of initiatives that appear to advance one individual’s reputation while creating work for everyone else. Share recognition generously. Mention the customer support manager whose observations clarified the problem, the analyst who found the data, and the compliance partner who helped design a safe test. This is not merely good manners. It signals that the project belongs to a group, not to a lone employee seeking attention.

At the same time, maintain ownership of the initiative’s momentum. Coalition building does not mean surrendering responsibility to the group. Someone must schedule the next conversation, summarize decisions, clarify open questions, follow up on commitments, and keep the original strategic purpose visible when discussions become fragmented. In many cases, that person is you.

The most successful intrapreneurs become trusted translators. They can explain a customer problem in language that resonates with operations, frame an experiment in terms that reassure risk teams, describe financial value in terms that finance can test, and give executives a concise view of the strategic opportunity. They do not pretend that every concern is unimportant. They connect those concerns to a practical path forward.

Your coalition does not need to begin large. It needs to begin real. One respected champion, one informed gatekeeper, one knowledgeable contributor, and one sponsor with a genuine stake can be enough to move a small experiment from conversation to action. From there, evidence creates influence. As results emerge, the coalition can expand.

Before you bring your idea into a formal decision meeting, ask yourself: Who will be affected by this? Who can stop it? Who can make it stronger? Who needs to be surprised by nothing? The answers will reveal the political work still ahead.

That work may not feel as exciting as developing the idea itself. Yet it is often the difference between an innovation that remains a thoughtful suggestion and one that becomes an organizational reality.

The Executive Pitch

By the time you are ready to seek executive support, you should have done more than develop an idea. You should have identified its strategic anchor, listened to the people closest to the problem, understood the concerns of likely gatekeepers, and begun building a coalition. The pitch is not a substitute for that work. It is the moment when you make that work visible, coherent, and actionable.

Executives are often portrayed as people with short attention spans. The reality is more demanding: they have limited attention because they are responsible for many consequential decisions at once. In a single day, they may move between financial performance, customer issues, operational risk, talent concerns, regulatory developments, and competitive threats. They do not need every detail of your initiative immediately. They need enough clarity to understand why the issue matters, why it matters now, what decision is required, and why you are prepared to lead the next step.

That is the purpose of storytelling in an intrapreneurial setting. It is not theatrical performance, and it is not the manipulation of facts. It is the disciplined arrangement of facts into a narrative that helps people see the problem, the opportunity, and the path forward.

A weak internal pitch usually begins with the solution. “We want to build a new portal.” “We need to introduce automation.” “Our team has designed a new process.” The speaker may then move quickly into features, implementation details, or a long list of possible benefits.

This approach makes executives work too hard. They must infer what problem the proposal solves, how it connects to strategy, and whether the requested investment is proportionate to the value. When the narrative is unclear, leaders often default to caution. They ask for more analysis, defer the decision, or conclude that the project is interesting but not urgent.

A stronger pitch begins where executive attention already exists: with a meaningful business problem.

Return to the example of the online application journey. The intrapreneur should not begin by describing a redesigned interface or a new digital tool. She might begin this way: “Our growth strategy depends on reaching underserved customer segments, yet a significant number of qualified applicants abandon the process before completion. Customer support records show that many are confused by the same steps, and the abandonment is particularly high among the segment we have identified as a priority.”

In a few sentences, she has established a strategic objective, a customer problem, and evidence that the problem is material. The executive does not yet need to agree with the proposed solution. They can first agree that the problem deserves attention.

The next part of the story makes the cost of inaction visible. This is essential because organizations are often more comfortable preserving a flawed current state than investing in an uncertain alternative. Your task is to show that doing nothing is also a decision, and one with consequences.

For example: “If we leave the journey unchanged, we will continue to spend marketing resources attracting customers who never complete an application, while support teams handle avoidable questions and competitors offer simpler alternatives. We are not only losing volume; we may be losing the trust of customers we are trying to serve.”

Notice that this statement is not exaggerated. It does not claim that the company will collapse without immediate action. It simply identifies the real operational, financial, and strategic cost of allowing the problem to continue.

Then introduce the opportunity in practical terms. “We believe a focused redesign of two high-friction stages could improve completion rates without changing the underlying approval process. Rather than funding a full rebuild, we propose a six-week pilot using the existing platform, limited to one customer segment.”

This is where the work of strategic alignment and coalition building becomes especially valuable. Because the intrapreneur has already spoken with customer support, digital product, compliance, and other relevant functions, she can demonstrate that the proposal is not an untested personal opinion. It is a considered, bounded experiment.

A persuasive executive story often follows a simple sequence:

• Here is the strategic priority.
• Here is the specific obstacle preventing progress.
• Here is the evidence that the obstacle is real.
• Here is the cost of leaving it unresolved.
• Here is a proportionate first step.
• Here is what we will measure.
• Here is the decision or support we need now.

This sequence protects you from a common intrapreneurial error: asking executives to approve a final destination when you only need permission to begin learning. In an uncertain environment, a large promise can create skepticism. A small, well-designed experiment can create confidence.

Your audience also matters. The core story should remain consistent, but the emphasis should change depending on who is in the room. A finance leader will want to understand the value hypothesis, the cost of the test, and the way results will be measured. A risk or compliance leader will want to know the boundaries of the experiment and the controls in place. A technology executive will care about architecture, capacity, security, and long-term ownership. A commercial leader may focus on customers, growth, and speed to market.

Adapting your message does not mean telling different stories to different stakeholders. It means translating the same initiative into terms that allow each person to assess it responsibly.

For the application pilot, a finance partner might hear, “The test uses existing tools and requires limited design capacity. We will compare completion rates, support contacts, and conversion quality against a baseline, so we can determine whether the benefit justifies broader investment.” A compliance partner might hear, “The pilot does not alter eligibility decisions, required disclosures, or approval criteria. We will validate all revised customer language before launch.” A technology leader might hear, “We are not introducing a new platform or creating a permanent integration. The pilot will use the current digital environment and will include a clear handoff plan if it succeeds.”

Each statement addresses a legitimate concern without losing sight of the central business opportunity.

Good storytelling also depends on specificity. Corporate language can make an initiative sound polished while making it impossible to understand. Phrases such as “unlocking synergies,” “driving transformational value,” or “leveraging an innovative ecosystem” may sound impressive, but they often conceal the very details leaders need to evaluate.

Use plain language whenever possible. Say what is happening, who is affected, what you propose to test, and how success will be recognized. If the initiative will reduce manual work, identify the work. If it will improve customer experience, identify the moment that frustrates customers. If it will create financial value, explain the mechanism through which that value appears.

A short example is often more memorable than a spreadsheet alone. You might say, “Today, a customer reaches the income-verification stage, sees unfamiliar terminology, leaves the process, and calls support the next day. The support agent explains the same issue repeatedly, but the customer must begin again. We can remove that friction at the point where it occurs.”

This human detail gives the data meaning. It should not replace evidence, but it can make evidence easier to remember. Executives are people. They respond to a credible story because it helps them connect abstract metrics to a real customer, employee, or operational reality.

At the same time, do not overload your pitch with information. A frequent mistake is to anticipate every possible question and answer all of them before anyone asks. This can bury the central message under process maps, technical specifications, historical background, and secondary benefits.

Your first communication should create clarity, not display the full extent of your research. Keep detailed analysis available as supporting material. Think of your pitch as the front door to the initiative, not the entire building.

A useful discipline is to prepare three versions of your story.

The first is a one-sentence strategic anchor, building on the discipline established earlier in this chapter. For example: “This pilot supports our growth strategy by reducing preventable abandonment in the application journey for a priority customer segment.”

The second is a one-minute version that explains the problem, the evidence, the proposed test, and the requested support.

The third is a five-minute version that includes the expected value, key stakeholder input, major risks, measurement plan, and next decision point.

If you cannot explain the initiative at each of these levels, you may still be too close to the details. Practice until you can speak clearly without sounding rehearsed. The goal is not to memorize a script. It is to know the logic of your case well enough that you can adjust naturally when the conversation changes.

The request itself should be direct. Many otherwise strong pitches end ambiguously. The intrapreneur explains the opportunity, receives polite interest, and leaves without knowing what happens next. Do not make executives guess what you need.

Say, “We are asking for your sponsorship of a six-week pilot, permission to use existing digital and analytics capacity, and agreement that we will return with results before requesting any scale investment.” Or say, “We need your help resolving ownership between the product and operations teams so that the pilot has a clear accountable leader.”

A clear ask makes it easier for a leader to say yes, no, or not yet. All three answers are more useful than vague encouragement.

Executive questions should be treated as invitations to strengthen the initiative, not as attacks on your credibility. When a leader asks, “Why now?” they may be testing urgency. When they ask, “Who will own this after the pilot?” they may be protecting the organization from an orphaned success. When they ask, “What happens if the test fails?” they may be assessing whether the downside is contained.

Answer honestly. If you do not know, do not invent certainty. Say, “That is the question the pilot is designed to answer,” or “We have not finalized the long-term owner, but product and operations have agreed to evaluate ownership before we recommend scaling.” Credibility grows when you distinguish between what is known, what is assumed, and what will be tested.

Finally, remember that the meeting is rarely the end of the pitch. Executive support is often built through a sequence of interactions: an informal conversation, a concise briefing, a formal decision meeting, a follow-up with additional data, and a later review of pilot results. Continue the habits that helped you build the coalition in the first place. Send a clear summary of decisions. Confirm owners and deadlines. Share progress without overwhelming people. Give credit to the contributors who made the work possible.

The most effective intrapreneurial pitch does not try to make an executive fall in love with an idea. It enables them to make a responsible decision to support a promising next step. It shows that you understand the company’s strategy, respect its constraints, have listened to the people who will be affected, and are prepared to learn before asking the organization to commit more.

When you can tell that story with clarity, evidence, and a precise request, you are no longer presenting an isolated idea. You are offering leadership a credible way to turn strategic intent into action.

Case Study: The Office of the Future That Xerox Did Not Sell

The situation. In 1970 Xerox, the copier company, opened a research center in Palo Alto, California, and gave it a bold assignment: invent the office of the future. The researchers delivered. By 1973 they had built the Alto, a computer meant for one person rather than a whole department. It had a graphical screen with windows and a pointer, and it could connect to other machines through a new kind of network called Ethernet. The same center developed laser printing.

What happened next. In December 1979, Steve Jobs and a team of Apple engineers visited the center. Xerox had arranged to buy a small stake in Apple, and in return Apple received demonstrations. What they saw confirmed the direction Apple was already exploring. Xerox did bring a computer to market in 1981, the Xerox Star, but it was expensive, and Xerox never became a computer company. To most of the world, the graphical interface came to look like Apple’s idea.

The other half of the story. One invention from the same lab succeeded spectacularly inside Xerox: the laser printer. Many of the center’s ideas never became products, but some generated billions of dollars in sales for Xerox. The difference is the lesson. The laser printer fit what Xerox already understood and already sold: putting marks on paper for offices. The personal computer asked Xerox’s leaders to become a different company.

The lesson for you. This chapter argues that intrapreneurs fail when they lead with the idea instead of the organization’s strategic priority. Xerox is the classic proof, at enormous scale. The researchers had the future in their hands. What they lacked was a bridge between the invention and the problems the company’s decision makers believed they were paid to solve. Before you ask whether your idea is good, ask whether the people who must fund it can see their own priority in it.

Chapters 2 through 4, the other three case studies, the Dictionary and the cut-out flashcards continue in the paperback.