IS Consulting vs. IS Academia: An Honest Comparison

When I was deciding whether to do a PhD, the choice I kept framing it as was "academia versus consulting." My advisor at the time gently pointed out that I was treating these as opposites when they are actually more like parallel structures with different incentives and different rhythms. He was right, but the differences are real enough that the comparison is still worth making honestly, because most people who make this choice do it without complete information on either side.

Both IS consulting and IS academia involve studying how organizations use technology. Both require you to read a lot, synthesize quickly, communicate to different audiences, and manage relationships with stakeholders who have their own agendas. If you are good at research design, at asking the right question before generating a lot of data, you are useful in both contexts. I have met consultants who think like researchers and researchers who would have been excellent consultants if they had gone that way. The core analytical skill is not that different.

Where things diverge is in the output, the timeline, and the lifestyle.

In consulting, the deliverable is a recommendation. The client paid for a conclusion. They want to know what to do. This seems obvious, but it has a deep effect on how you work. You do not get to say "it depends" for very long before someone in the meeting loses patience and asks you to pick a direction. You develop a tolerance for making confident recommendations with incomplete information. You learn to be useful fast, because the engagement has a fixed timeline and the partner on the project is billing hundreds of dollars an hour. The upside is immediate feedback. You produce something, someone acts on it, you can see whether it worked. The financial compensation is also better, especially early. The downside is that most consulting work does not accumulate into a body of knowledge. One project does not build on the last one in any systematic way. You learn a lot, but your learning is privately held.

Academia works almost exactly backwards. The deliverable is a paper. The paper goes through a review process that can take one to three years between submission and publication. Reviewers will reject it for reasons that range from substantive and fair to arbitrary and wrong. You resubmit somewhere else and the clock starts again. The whole system requires a tolerance for delayed gratification that borders on pathological. And then the paper comes out, maybe a few hundred people read it, and you start the next one. The financial compensation is lower on the front end and stabilizes (assuming tenure) into something reasonable but rarely lucrative. The trade is that your work accumulates. Each paper builds on the last. Your ideas get into the literature, other people cite them, the knowledge compounds over years.

The skills that transfer between the two paths are the ones I mentioned: research design, synthesis, communication, stakeholder management. IS researchers who go into consulting tend to bring a discipline around questions that many consultants lack. They ask "what do we actually know about this?" before jumping to frameworks. IS consultants who move into research (and some do) bring a directness and a practitioner intuition that enriches their empirical work.

The skills that do not transfer cleanly are the ones that get socialized into you by the environment. Academics hedge everything. This is not a character flaw. It is the correct response to the norms of scientific communication, where overclaiming will get you in trouble with reviewers and with your own conscience if you care about accuracy. But "the effect is positive and significant under certain conditions with important boundary conditions depending on how you operationalize the construct" is not a useful answer when a client needs to decide by Thursday. Consultants get trained out of hedging fast. Academics get trained into it at about the same pace.

There is also the question of what kind of intellectual life you want. Academia offers more freedom to choose your problems. Nobody tells me what to study. My research agenda is mine. The trade is that the audience for academic work is narrow. A good paper in MIS Quarterly or Information Systems Research will be read carefully by a few hundred IS scholars. A well-positioned consulting report might influence a Fortune 500 company's IT strategy. The impact mechanisms are completely different, and I do not think one is obviously superior. It depends on what you mean by impact.

The piece nobody talks about honestly is the lifestyle difference. Academic job searching is brutal and geographically constrained. You apply to a small number of openings, you wait months for decisions, and you may need to move to a city you did not choose. The entire early-career period involves constant evaluation. Consulting hiring is faster and geographically flexible. Mobility within the firm is real. The lifestyle is intense in a different way: travel, client demands, and billable hours create pressure of their own kind.

My honest take, as someone who chose academia, is that I chose it partly for the questions and partly for the rhythm. I like working on a problem for two years and caring about getting it right, not just getting it done. I like the writing. I like the fact that what I produce stays in the world and can be read by someone ten years from now. I also know that I would have been capable of building a good consulting career and that I am not making the objectively correct choice, just the one that fits how I want to spend the next thirty years. Most people who make this choice well are making the same kind of self-assessment.

What I wish someone had told me earlier is that the choice is more about identity than skill. The question is not "which path will I be better at?" It is "which version of working hard do I want to do?"