About Jeffrey Erens
Professional Journey and Background
My professional path began somewhat unconventionally in 2008 during the financial crisis, when traditional career trajectories were disrupted and adaptability became essential. After completing my undergraduate degree in economics from a mid-tier state university, I joined a regional financial services firm as a business analyst rather than pursuing the typical consulting or investment banking routes my peers favored. This decision, driven partly by limited options during the recession, proved formative because it exposed me to how real businesses operate under pressure rather than the sanitized case studies taught in academic settings.
Those early years from 2008 to 2011 involved analyzing loan portfolios, assessing credit risk, and watching firsthand as companies struggled with liquidity crises and operational challenges. I reviewed financial statements for hundreds of businesses across manufacturing, retail, healthcare, and service sectors, developing an intuitive sense for what separates sustainable operations from those heading toward distress. The patterns became clear: companies that survived had strong unit economics, diversified customer bases, adequate cash reserves, and leadership willing to make difficult decisions quickly rather than hoping circumstances would improve on their own.
The transition to consulting happened in 2012 when a former colleague recruited me to a healthcare technology firm that needed someone who understood both financial analysis and operational realities. This role involved implementing electronic health record systems and practice management software for medical groups ranging from single-physician offices to multi-specialty practices with 40+ providers. The technical implementation was straightforward, but the change management proved extraordinarily difficult. Physicians resisted new workflows, staff struggled with training, and many implementations failed not due to technology limitations but because of inadequate attention to the human factors involved in organizational change.
This realization shifted my focus toward understanding why smart people in well-resourced organizations struggle to implement beneficial changes. I pursued additional education through executive programs at Stanford and MIT between 2014 and 2017, studying organizational behavior, change management, and systems thinking. These frameworks provided vocabulary and structure for phenomena I'd observed empirically but couldn't fully explain. The combination of practical experience and theoretical grounding created my current approach, which emphasizes evidence-based diagnosis, realistic implementation planning, and continuous adaptation based on feedback rather than rigid adherence to predetermined plans.
By 2019, I had accumulated enough experience and credibility to establish an independent practice rather than working within larger consulting firms. This independence allows me to be selective about engagements, focusing on situations where I can deliver genuine value rather than accepting any project that comes along. The past five years have involved work with 47 different organizations across technology, healthcare, manufacturing, professional services, and e-commerce sectors. Each engagement adds to my pattern recognition abilities and reinforces or challenges assumptions about what works in different contexts. For more specific information about my services and approach, visit the main page, or if you have questions about working together, check the FAQ page.
| Year | Program/Certification | Institution | Focus Area |
|---|---|---|---|
| 2004-2008 | B.A. Economics | State University System | Economic theory, quantitative analysis |
| 2014-2015 | Executive Program - Strategic Management | Stanford Graduate School of Business | Corporate strategy, competitive analysis |
| 2016-2017 | Professional Certificate - Systems Thinking | MIT Sloan School of Management | Organizational dynamics, complex systems |
| 2018 | Certification - Change Management | Prosci | Change methodology, stakeholder engagement |
| 2020-2021 | Executive Education - Digital Transformation | Harvard Business School Online | Technology strategy, digital business models |
Core Values and Operating Principles
My work is guided by several non-negotiable principles developed through experience with what creates lasting value versus what generates short-term activity without meaningful outcomes. First, honesty over agreeability means I provide direct assessments even when they're uncomfortable. If an organization's strategy is flawed, leadership is ineffective, or a proposed initiative is unlikely to succeed, I say so clearly and explain why. This approach occasionally costs me engagements when clients prefer consultants who validate existing beliefs, but it prevents wasting time and resources on doomed initiatives.
Evidence-based decision making represents the second core principle. Business involves uncertainty, but too many decisions rely on intuition, conventional wisdom, or mimicking competitors rather than analyzing actual data. I push organizations to test assumptions, measure results, and adjust based on evidence rather than opinions. This doesn't mean analysis paralysis; sometimes you need to make decisions with incomplete information. But it does mean being explicit about what you know, what you're assuming, and what signals will indicate whether your assumptions are correct.
The third principle involves sustainable implementation rather than impressive presentations. Consulting has a reputation problem because many firms excel at creating beautiful slide decks and strategic frameworks that never translate into operational reality. My deliverables emphasize actionability over aesthetics. A strategic plan isn't valuable because it's comprehensive or elegantly written; it's valuable if people can use it to make better decisions and take effective actions. This means recommendations must account for organizational capacity, political realities, resource constraints, and change management requirements, not just theoretical best practices.
Client capability building forms the fourth principle. My goal isn't creating dependency where organizations need to hire me repeatedly for the same issues. Instead, I aim to transfer knowledge and develop internal capabilities so clients can handle similar challenges independently in the future. This involves explaining my reasoning, teaching analytical frameworks, and involving client team members throughout the engagement rather than disappearing to create recommendations in isolation. While this approach might reduce repeat business, it generates referrals and aligns with my actual objective: helping organizations become more effective rather than maximizing my consulting revenue.
Finally, I maintain realistic optimism about what's possible. Most organizational challenges are solvable, but solutions require time, resources, and commitment. I'm optimistic that organizations can improve significantly with proper diagnosis and implementation. However, I'm realistic that transformation takes 12-24 months minimum, requires difficult tradeoffs, and demands sustained leadership attention. Promising quick fixes or revolutionary results sets false expectations and leads to disappointment. Better to set realistic targets and exceed them than promise dramatic outcomes and fall short.
| Core Principle | What It Means in Practice | What I Won't Do | Typical Client Benefit |
|---|---|---|---|
| Honest Assessment | Direct feedback on challenges | Validate flawed strategies for fees | Avoid wasting resources on bad ideas |
| Evidence-Based Decisions | Data-driven recommendations | Rely solely on intuition or trends | Higher success rate on initiatives |
| Sustainable Implementation | Actionable, realistic plans | Create impressive but unusable deliverables | Actual operational improvements |
| Capability Building | Knowledge transfer throughout | Create dependency on consultant | Internal team development |
| Realistic Optimism | Honest timelines and expectations | Promise quick fixes or guarantee results | Appropriate resource allocation |
Working Style and Collaboration Approach
My working style emphasizes collaboration rather than the traditional expert-consultant dynamic where recommendations are delivered from on high. The most effective engagements feel like partnerships where I bring external perspective, analytical frameworks, and cross-industry experience while clients contribute deep organizational knowledge, industry expertise, and implementation ownership. This collaborative approach requires mutual respect and open communication in both directions.
I'm direct in communication style, which some people find refreshingly clear and others perceive as overly blunt. My goal is efficiency and clarity rather than softening messages with excessive diplomacy. If something isn't working, I'll say so explicitly and explain why. If I don't know something, I admit it rather than bluffing. If a client's idea has merit, I'll support it enthusiastically. This straightforward style works well with confident leaders who value candor but can create friction with those who prefer more indirect communication or need extensive relationship building before accepting critical feedback.
Regarding work habits, I'm highly responsive during active engagements, typically replying to emails within 4-6 hours during business days and making myself available for urgent issues. I maintain regular communication cadences with weekly updates and bi-weekly check-in meetings to ensure alignment and address obstacles promptly. However, I'm also protective of deep work time needed for analysis and strategic thinking, so I batch communications rather than maintaining constant availability. This balance between responsiveness and focused work time allows me to deliver both accessibility and high-quality analytical output.
I work with small teams or independently rather than bringing large consulting teams to engagements. Most projects involve just me, occasionally supplemented by specialized expertise for technical areas outside my core competencies (such as IT infrastructure, legal compliance, or specialized financial modeling). This lean approach reduces costs for clients and ensures consistency in quality and approach. It does mean I'm selective about engagement timing and can only work with a limited number of clients simultaneously, typically 3-5 active projects at any given time.
The collaborative approach extends to how I handle disagreements or obstacles. When clients push back on recommendations, I view it as an opportunity to test my thinking rather than a challenge to my expertise. Sometimes client objections reveal considerations I missed or organizational realities that make my initial recommendation impractical. Other times, discussion helps clients understand the reasoning behind recommendations they initially resist. Either way, the dialogue improves outcomes compared to simply accepting or rejecting recommendations without discussion. Additional information about my background and experience can be found throughout this site, and the FAQ page addresses common questions about engagement processes and expectations.
| Factor | My Approach | Works Well With | Potential Friction With |
|---|---|---|---|
| Communication Style | Direct and candid | Confident leaders valuing honesty | Those preferring indirect feedback |
| Decision Making | Evidence-based, analytical | Data-driven organizations | Highly intuition-driven cultures |
| Engagement Model | Collaborative partnership | Organizations wanting capability building | Those expecting consultant to do everything |
| Work Pace | Balanced - responsive but focused | Realistic timelines, patient leadership | Demand for instant results |
| Team Size | Small, lean engagements | Cost-conscious, hands-on clients | Those expecting large consultant teams |