Fractional VP of Product Design and AI Strategy

A consultant assesses and recommends. A fractional VP diagnoses, decides and delivers. The difference is accountability and hands-on implementation, not just action plans in presentation decks.

Most consulting engagements follow a familiar pattern: discovery, analysis, a presentation of findings, a set of recommendations and an invoice. What happens after the consultant leaves is someone else’s problem. That model works well for isolated strategic challenges. It breaks down when the organization needs someone to actually implement the answer, manage the team through the change and be accountable for the outcome.

A fractional engagement works differently. The approach is developed collaboratively with your management team and the people directly affected, not handed down from outside. The fractional VP is in the meetings, in the decisions, in the work alongside your teams. The scope is agreed upfront. The outcomes are defined at the start. And the engagement doesn’t end when the deck is delivered. It ends when the solution is up and running.

Perhaps, but the calculus has changed. The traditional VP hire assumes a stable, well-defined role that justifies a 4–6 month search, $250–350K+ in total compensation before equity and a 90-day ramp before anyone is fully productive, all with no guarantees.

In 2026, most organizations don’t have that kind of time or tolerance for risk. AI implementation mandates, restructuring pressures and evolving team structures mean the leadership need is immediate and the job definition is still forming.

A fractional engagement is often the right answer in situations like these:

1. Planned leadership gap. An executive retiring, finishing out a major program or taking extended leave, continuity is needed without committing to a permanent replacement or hire.
2. Unexpected departure. A key leader left suddenly and the team is without direction in the middle of critical program or initiative.
3. Test before you hire. The organization wants to know if a permanent VP-level role is actually needed before recruiting for one. A fractional engagement onboards the mission, sets up the function, defines the role and hands it off to a permanent hire who steps into a running operation rather than a blank page and pressing deadlines. A fractional exec can even help with the recruitment and onboarding of the full-time role.
4. M&A integration. Two product and design organizations need to be integrated, a situation that requires senior leadership but may not warrant a permanent hire once the work is done.
5. Post-funding standup. A new funding round requires standing-up a design and product function quickly, before there’s time to recruit the right permanent leader.
6. High-stakes deliverable. A demo, board presentation, customer pilot or mission-critical usability testing needs design and prototype work delivered fast, without the ramp-up time a new hire would require.
7. AI implementation mandate. Leadership has committed to AI adoption but the organization lacks the senior expertise to assess readiness, select the right tools, integrate them into existing workflows and bring the team along without disruption. The fractional engagement covers the full arc, from diagnostic through to sustainable adoption.
8. Building a practice from zero. The organization requires a design or product function that doesn’t exist yet, exists only informally, needs process and rigor implemented or has designers and product people scattered across teams with no unified direction. Someone with experience in all of these critical roles needs to stand it up, define the structure, hire or re-task the team, establish the processes and get it running before a permanent leader takes over.

In each case, senior leadership is available immediately with the flexibility to define and fill key roles based on what’s actually required at the time of “boots on the ground” rather than what was assumed at the start of a search.

It’s a fair question and the honest answer is: it depends on what the challenge actually is.

If the challenge is a specific, contained task such as drafting a document, summarizing research or generating initial concepts, a capable manager with the right AI tools can absolutely handle that. No argument.

But, there’s a deeper point worth discussing: AI capability is spreading fast. While most organizations have access to the same models, the same tools, the same raw intelligence. The differentiator is no longer what the AI can do, it’s how the organization is designed to use it. That’s an execution and workflow design problem. It requires the kind of judgment and experience that comes from having built effective teams, delivered successful solutions and rescued at-risk programs across Fortune 100 firms.

The fractional model addresses a different set of challenges:

• Organizational authority. What senior leadership brings isn’t just knowledge, it’s the credibility to make decisions stick, align teams behind them and be accountable for results. AI doesn’t confer that.
• Judgment built from experience. Knowing which process to implement, which stakeholder dynamic is the real blocker, which team structure will hold up in six months, that comes from having done this repeatedly across different organizations. AI can assist that judgment, but it can’t replace it.
• Change management. The hardest part of any transformation is getting people to change how they work. That’s a human problem. It requires trust, communication and someone with the experience to anticipate resistance before it surfaces.

That’s a reasonable assumption, but the dynamic often runs the other way. A new VP hire spends the first several months learning the culture, building internal relationships, establishing political capital and aiming to prove that their hire was the right decision by not ticking anyone important off. During that time, the instinct is to be cautious, align with existing power structures and avoid positions that could create friction. That’s very human, rational behavior. It’s also expensive for the organization.

A fractional practitioner arrives with no political debt, no internal alliances to protect and no concern about the next performance review. The only agenda is delivering the outcome the engagement was hired for. That freedom to advocate for the right decision rather than the safe one is one of the less obvious but more valuable aspects of the model.

The accountability is also structured differently. A fractional practitioner’s next engagement depends entirely on the results of this one. And if the approach isn’t working, the organization isn’t locked in; the engagement ends cleanly at the next renewal point. No severance, no HR process, no awkward transition period. That’s a level of risk management a full-time hire simply can’t offer.

It depends upon the scope of the mandate and our agreed-upon success metrics, but most engagements run 6–12 months. Some extend to 18 months for ongoing strategic oversight. The minimum is 3 months, enough time to diagnose, stabilize and begin building. After that it’s month-to-month.

Typically within 1–2 weeks of agreement when capacity is available. During periods of full client load, the wait may extend to 4–6 weeks or longer. If startup timing is critical, the initial conversation will clarify availability and help determine whether the timeline works for your situation.

Availability is structured around the engagement scope agreed at the start, typically 2–3 days per week embedded, with async availability throughout. Early-stage engagements tend to run at a higher intensity during the diagnostic phase. As the practice scales, availability windows are defined more specifically by the client. If your situation requires intensive early availability or a specific weekly cadence, that gets built into the engagement terms upfront, not figured out after the fact.

Defined at the start, not the end. Success criteria are agreed in the first 30 days and reviewed at each phase. The engagement kickoff includes a standard set of diagnostic tools, onboarding templates and process frameworks built from 20+ years of transformation work, so the first meeting is productive, not administrative. That package also includes a customizable announcement template for introducing the engagement to affected teams, a stakeholder alignment framework and a 90-day milestone tracker. The goal is to remove every “now what?” moment before it happens.

Every organization handles this differently and there’s no single right answer. Some introduce the engagement formally with a company-wide announcement. Others prefer a quieter roll-out with a direct introduction to the core team and key stakeholders with broader awareness building organically as the work progresses. The title used internally is entirely your call and doesn’t need to match any formal designation.

What does come standard with every engagement is a customizable announcement template designed to introduce the engagement to affected teams clearly and confidently, explain the scope and set expectations from day one. The goal is to make sure no one on your team is left wondering who this person is, why they’re here or how long they’re staying.

Typically minimal. The engagement is structured as a professional services contract between the two firms rather than an employment relationship. That means no payroll processing, no benefits administration and no W-2. A W-9 is provided at engagement setup for your records, and a 1099-NEC is issued at year end if applicable. A standard services agreement and NDA cover the legal side.

Whether HR needs to be looped in depends on your organization’s internal policies around contractor and vendor management. Some clients run it entirely through procurement, others prefer HR visibility for team communication purposes. Security and system access requirements are addressed during engagement setup. See the equipment and licensing question below.

Confidentiality is covered by NDA as part of engagement setup, either a standard Mark Phelps LLC agreement or the client’s preferred document, whichever is simpler for your organization. Work product, strategic decisions and internal dynamics stay internal.

Equipment, licensed software and system access requirements vary by engagement. Some clients provide company hardware or licensed seats for security or compliance reasons, particularly in regulated industries where data handling policies require it. Others prefer BYOD. For system access, standard user-level permissions are typically sufficient. Administrative or elevated access is only requested when the scope specifically requires it and is documented in the engagement agreement.

Communication access is set up as part of the kickoff, typically a company email alias, Slack or Teams access and calendar integration with key stakeholders. The goal is to be operationally indistinguishable from an internal team member from day one. No additional equipment or licenses are required from the client unless that’s the preference. The approach is whatever makes the engagement run cleanly for your organization from day one.

The common thread isn’t industry, company size or where the need sits in the organization. It’s a specific, high-stakes design and product leadership challenge that can’t wait for a full-time hire.

The practice has the deepest track record in financial services, wealth management, insurance and MedTech industries where regulatory complexity, high-stakes UX and organizational scale all intersect. But the organizational challenges that fractional leadership solves aren’t industry-specific. Scaling teams, integrating AI, standing up a design function, navigating M&A, these challenges look similar whether the product is a wealth management client dashboard, insurance customer portal or a surgical navigation platform.

That’s worth a conversation. Sometimes organizations think they need a VP when what they actually need is a clearer process, a stronger team foundation, a subject matter expert or a more focused scope first. A 30-minute call will surface which it is.

And if fractional VP leadership isn’t the right fit, at least right now, that’ll be the honest answer. There’s no benefit to either party in proposing an engagement that doesn’t fit the need and the risk of mismatch is high. In some cases the right recommendation is a shorter diagnostic engagement first, or a specific service rather than ongoing embedded leadership. The goal is the right solution, not the biggest one.

That’s a common situation and there’s support built in for it. Beyond the standard engagement proposal, a customized business case document can be prepared specifically for your organization, built to your context, framed for your leadership audience and designed to help your internal champion make the case without having to build the argument from scratch.

The document covers the problem being solved, the fractional model rationale, expected outcomes and a cost comparison against a full-time hire. It’s written to answer the questions a CEO, CFO or board member will likely ask.

If a formal board presentation is needed, that conversation happens before the engagement begins, not after. The goal is to make sure the people who need to say yes are aligned from the start.

For larger engagements, yes. Rather than having your internal champion translate the proposal secondhand, a direct board presentation removes the telephone game and tends to accelerate the decision. I would be available to present alongside your champion, address questions directly and leave the board with a clear picture of the engagement scope, expected outcomes and cost rationale.

This option is scoped during the initial briefing call. Travel and reasonable expenses are covered by the client. It’s not appropriate for every situation, but for high-stakes or larger-scope engagements it’s often the fastest path to a confident yes.

Yes, and the AI background is more relevant than it might first seem. Most organizations hiring fractional leadership in 2026 will face AI questions whether they plan to or not. How the team will implement and manage AI-based tools and adapt their workflows, whether the product roadmap accounts for AI capabilities, what expectations customers have around AI use. These surface fast and having a leader who can handle both the organizational build and the AI strategy questions simultaneously saves the conversation you’d otherwise have to have separately. If the engagement is purely process and team-building with no AI component, the background doesn’t get in the way. It just means there’s capacity available if the need arises.

It depends on the scope agreed at the start. For many engagements, AI implementation is a natural part of the work: assessing readiness, selecting and integrating tools, embedding AI into existing workflows and building the team’s capability to sustain it. For others, the mandate is purely organizational leadership: building the team, establishing process and governance, and handing off to a permanent hire. Both are valid starting points.

If AI implementation is a priority, it gets scoped into the engagement explicitly rather than assumed. The conversation at the start determines what’s in and what’s not. For a full breakdown of standalone AI implementation services, see the Services page.

Fractional practitioners operate differently than salaried executives. There’s no base salary, no tenure and no performance review cycle to wait for, my next engagement depends entirely on the results of this one. That dynamic creates a level of accountability that’s difficult to replicate in a full-time hire. The reputation is the business. Every engagement either earns the next one or doesn’t.

The fractional model includes both the strategic leadership and the hands-on delivery work most organizations need alongside it. Depending on the engagement scope, this can include:

1. Product vision and discovery. Defining what the product should be, for whom and why, before a pixel is placed or a line of code is written. Includes market and user research, competitive analysis, opportunity framing and the translation of business goals into a product direction that teams can build toward with confidence.
2. Business and product stakeholder integration. Building the systems, cadences and communication frameworks that keep business stakeholders, product teams and design aligned throughout development and delivery. Replaces the ad-hoc escalations and late-stage surprises that slow decisions and create rework with structured collaboration that surfaces the right conversations at the right time.
3. Agile and sprint programs. Setup and facilitation, including sprint planning, backlog grooming, retrospectives and the integration of design cycles with engineering delivery. Built around how your organization actually works, not a generic Agile playbook.
4. Requirements and DevOps. Discovery, requirements gathering and DevOps / Jira process integration, translating design and product decisions into stories, acceptance criteria and hand-off documentation that development teams can actually use.
5. Lean UX and design review systems. Process design and iterative design review cadence setup, replacing ad-hoc feedback loops with structured, repeatable review cycles that keep stakeholders aligned and decisions moving without design-by-committee paralysis.
6. Design system. Research, planning, creation and governance, from the initial audit of what exists to the build of a component library that scales. Includes AI-assisted curation and prioritization of components, adoption strategy and the documentation that keeps it alive after the engagement ends.
7. AI readiness assessment. Stakeholder interviews, workflow audit and AI opportunity analysis, identifying where AI can deliver measurable ROI for your specific team before any tools are purchased or deployed.
8. AI tool selection and implementation. Evaluation of the most effective AI tools for your actual workflows, team capability and budget, followed by hands-on implementation and adoption support. Tool-agnostic, the recommendation is based on fit, not vendor preference.
9. AI workflow integration. Embedding AI into existing discovery-to-design-to-development processes, sprint workflows, hand-off documentation, review cadences so adoption is structural rather than optional and individual.
10. Team stand-up and building. Planning, justification and budgeting, including job description development with HR, hire parameters and salary banding with recruiting, through to candidate evaluation, onboarding and ramp-up. Actionable analysis on when, and when not, to grow a team and with which types of experience and skills. The goal is a team that runs on its own, not one that needs ongoing outside management to function.
11. Team culture and re-engagement. When a team has lost direction, confidence or trust in leadership, the first job is listening before leading. Diagnosing what’s actually broken, whether it’s unclear goals, misaligned expectations, poor process or the aftermath of a difficult leadership transition, then rebuilding the foundation that lets capable people do their best work again. Works in close partnership with HR where appropriate, while addressing the organizational and leadership dynamics that HR alone typically can’t resolve.
12. Stakeholder alignment. Design review frameworks and governance processes, establishing clear decision rights, structured review cadences and escalation paths that engage early buy-in, reduce late-stage rework and keep cross-functional friction manageable.
13. Usability testing. Usability practice stand up with testing program planning, execution and findings report-out mechanisms, including test design, participant recruitment, session facilitation and synthesis. Building the capability, processes and team knowledge to sustain it after the engagement ends, not just running a one-time study.
14. Research. Market and competitive research, including user research, persona development, journey mapping and stakeholder interviews to build the evidence base that drives design and product decisions. Not a one-time deliverable but an ongoing capability that informs the work throughout the engagement.
15. Documentation. UI documentation, including annotated wireframes, interaction specifications and design hand-off packages, and regulatory submission preparation for FDA 510(k), HE75 human factors and other compliance frameworks. Built to the standard development teams and regulatory bodies actually require, not just good enough to get by.

The engagement scope is agreed upfront. Some clients need the full stack. Others need one or two specific capabilities. The conversation at the start defines what’s in and what’s not.