Consulting On The Inside Beverly Scott

Internal Consulting as a Career Path: What It Actually Looks Like

I spent about six years working as an inside consultant before moving into a different role. The short version is that you operate like a consultant but your client is always your own employer or a related division within it. The long version is that it is one of the most poorly understood career tracks in most organizations, and the people who figure it out usually stumble into it rather than planning it deliberately. The basic setup involves someone in an internal role who takes on advisory or problem-solving assignments across departments. You are not external. You do not bill hourly. You do not have a clear promotion ladder that anyone can point to on a whiteboard. You exist in a gap between strategy teams, operations, and the people who actually execute things, and that gap is simultaneously the source of your value and your main source of frustration.

What Consulting On The Inside Beverly Scott Means in Practice

Beverly Scott wrote about this concept in ways that helped legitimize it as a career option rather than just a weird job title people used when they did not know what to call themselves. The core idea is that you can build a consulting practice within an organization instead of outside it. You learn the terrain. You build trust. You solve problems that would normally require bringing in an expensive external firm. The difference between reading about it and actually doing it is substantial. When you are inside, you have access to information that external consultants spend months trying to acquire. You also have baggage. People know your history. They know who you worked with before. They know which projects failed and why. An external consultant walks in clean. You walk in with a reputation that predates the current problem you are being asked to fix. This is not usually discussed in the literature around the topic. I learned this the hard way in 2018 when I was brought in to help a regional division restructure their project intake process. The external consultants who had preceded me left behind a twelve-page report that was technically accurate and completely unusable. The problem was not the analysis. The problem was that none of the recommendations accounted for the fact that the division director's budget cycle operated on a completely different timeline than the corporate finance team's. My workaround was to skip the formal process redesign for three weeks and instead map out every handoff point between the two teams while they were actually working through a live budget request. The friction points became obvious after about four meetings. We rebuilt the process around those actual touchpoints rather than the org chart on the wall. It cut the approval cycle from eleven days to four.

How the Role Actually Functions Day to Day

You are hired or assigned to specific problems. Sometimes these are announced initiatives. Often they are quiet fires that someone in leadership noticed but does not have the bandwidth to address directly. You diagnose, propose, and sometimes implement. The implementation part is where most inside consultants get stuck because they have authority without direct reports. You influence people who do not report to you. You have accountability for outcomes but rarely the budget to reward the people doing the work. The work tends to fall into three buckets. Strategic alignment projects where you help a division figure out what it actually does versus what it claims to do. Operational improvement assignments where processes are broken and slow. And organizational change work where leadership wants to shift culture or structure and has no idea how to start. Each bucket requires a different skill set. The strategic work needs comfort with ambiguity and executive communication. The operational work needs process mapping and metrics literacy. The change work needs patience and a thick skin. Most people who end up in this role did not apply for it. They got pulled in because they were good at connecting dots between teams and someone in management noticed that you kept volunteering for cross-functional assignments. Once you are in, you can formalize the role or let it happen informally. The formalized version usually comes with a title like internal consultant, business advisor, or strategic programs manager. The informal version is more common and usually involves you doing consulting work on top of your actual job description until someone either promotes you into it or complains that you are not doing your real job.

What You Need to Actually Be Good at This

Technical skills matter less than people assume. I have seen people with MBAs struggle here while others with completely unrelated backgrounds thrived. The differentiators are diagnostic speed, political navigation, and the ability to translate between executives who speak in strategy and the people who speak in daily tasks. If you cannot explain why a process change matters to a frontline worker in a sentence that does not include the word synergies, you will fail regardless of how polished your PowerPoint is. You also need to understand how decisions actually get made in your organization versus how the company handbook says they get made. This is non-negotiable. I watched a colleague once spend six weeks building a recommendation framework for a client approval process that was theoretically perfect. The framework failed because it assumed decisions flowed through a committee that did not exist in any operational reality. The real decision maker was a senior VP who had never attended a single committee meeting but received informal weekly updates through email. Correcting that took about four hours once we figured it out. The wasted six weeks could have been avoided with two conversations with people who had been there longer than I had.

Downsides No One Talks About

The role has structural weaknesses that make it difficult to sustain long term. Compensation rarely matches external consulting pay for comparable work. There is limited visibility outside your own organization because your accomplishments are often framed as internal projects rather than standalone achievements. Job security depends entirely on leadership's willingness to maintain an internal consulting function, which tends to disappear first during budget cuts because nobody can easily quantify what you add until something breaks. You also risk becoming the person who gets called in to clean up other people's mistakes without having the authority to prevent those mistakes in the first place. This happens constantly. You are brought in after a strategy fails, asked to figure out what went wrong, and expected to fix it while being told that you should not revisit past decisions because leadership wants forward momentum. The position is structurally contradictory. You need historical context to diagnose problems accurately but political constraints that discourage digging into recent history. If you are considering this path and want something more structured with clearer advancement, program management or product management roles offer more defined career ladders. If you prefer advisory work without the internal politics, external consulting firms provide more straightforward compensation models and exit opportunities. Internal consulting works best when you already have deep institutional knowledge and relationships, when your organization genuinely values cross-functional problem solving, and when you are comfortable operating in roles that are partially undefined.

The people who last in this role tend to be the ones who treat it as a series of discrete projects rather than a permanent identity. You move in, solve something real, document what worked and what did not, and then either escalate into a more senior advisory position or transition to a different type of role. Staying too long without deliberate movement usually results in becoming the go-to person for everything and respected by nobody in particular.