Approach: The Forward Deployed Engineering model

Logevon's engineers work inside your business, build the solution with your team, and hand over what your team needs to run it.

Definition: What Forward Deployed Engineering is

FDE

Forward Deployed Engineering (FDE) is a delivery model in which engineers work embedded with a client's teams and business environment to understand the problem, build the solution within existing systems and transfer the knowledge needed to operate it.

  • It starts from a business problem, not a specification.
  • It is built with the client's team, inside existing systems.
  • Documentation and knowledge transfer are in scope.

FDE is not staff augmentation or outsourcing. At Logevon it is not a service but the delivery model for all three services.

Process: The six stages

The six stages of Logevon's FDE delivery model are Understand, Assess, Design, Build & Integrate, Enable & Transfer, and Improve.

  1. Understand

    Logevon's engineers work with your operational and technical teams to learn the process, the systems behind it and the goal.

    You getA written problem statement your teams agree on.

  2. Assess

    We examine the existing systems, data and constraints, then weigh the options, including the smallest change that would work.

    You getA documented assessment: risks, options and a recommendation.

  3. Design

    We design an architecture sized to the problem and to what your team can maintain, and review it with them.

    You getAn architecture and delivery plan, with scope and handover defined.

  4. Build & Integrate

    Your team and ours build in the same codebase and connect the solution to the systems you already run, in working increments.

    You getWorking software in your environment, integrated with existing systems.

  5. Enable & Transfer

    We hand over documentation, technical understanding and working practices to your team, deliberately and while the work is still under way.

    You getArchitecture and operations documentation, and a team that has done the work.

  6. Improve

    We measure the result against the original goal, refine what falls short, and reduce our involvement as your team takes over.

    You getResults measured against the goal, and a backlog your team owns.

The stages set an order of work, not a timeline.

Handover: What stays with you

We don't build dependency. We build capability.

Capability building is strengthening a client's internal teams, knowledge and systems so the organization can operate and evolve its solutions itself.

A working solution

Software that works in your environment, integrated with the systems you already run.

Documentation

Architecture decisions, system design and operating procedures, written during the work, not after it.

A capable team

Your people built the solution with us and are ready to run and extend it.

Ownership

Your code, data and intellectual assets stay under your control, per the agreed terms.

Comparison: How FDE differs from staff augmentation and outsourcing

FDE differs from staff augmentation and outsourcing in who directs the work, who is accountable and what the client keeps.

How FDE differs from staff augmentation and outsourcing
FDEStaff augmentationOutsourcing
Who directs the workLogevon and the client, jointlyThe clientThe provider
Who is accountableLogevon, for the problem-solving processThe clientThe provider, per the contract
Knowledge transferIn scope from the startOrganized by the clientDepends on the contract
What remains afterwardsWorking solution, documentation, capable teamThe work done under client directionThe delivered work or service
When it fitsA defined problem needing joint workA managed team that needs capacityA function or deliverable to hand off

Different models suit different needs. For a fuller guide to choosing between them, see Forward Deployed Engineering vs staff augmentation.

Fit: When FDE fits, and when it does not

FDE fits when

  • The problem is tied to how your operations and systems work.
  • People from your team can take part throughout the work.
  • You want to run and extend the result yourselves.
  • The solution has to work with systems already in place.

FDE does not fit when

  • You only need extra developer capacity under your own management.
  • The work is a fixed specification to build and hand back.
  • No one from your organization can take part.

When Forward Deployed Engineering is the wrong choice covers the second list in more detail.

Services: Where we apply it

Logevon delivers all three services through FDE.

All solutions

FAQ: Questions about working this way

How does an engagement start?

An engagement with Logevon starts with a conversation about a specific problem, not with a proposal. If the problem suits FDE, work begins with the Understand and Assess stages. Scope is then defined around an outcome and a handover.

Does Logevon stay involved after handover?

Logevon may continue to support a client after handover when that is needed. Ongoing dependency is not its business objective, so each engagement is planned for your team to take over.

What does knowledge transfer include?

Knowledge transfer is the deliberate handover of documentation, technical understanding and working practices from the delivery team to the client's internal teams. Your team takes part throughout delivery, so much of the transfer happens during the work. It is in scope from the start, not added at the end. Knowledge transfer in Forward Deployed Engineering sets out what passes at each stage.

Who owns the code, data and intellectual property?

The client keeps control of its code, data and intellectual assets, per the agreed terms. The terms are set out in the contract for each engagement.