Why Forward Deployed Engineering Needs Industry Context

Faruk Muratovic, Deloitte Engineering leader and principal, Deloitte Consulting LLP.

getty

Every enterprise has access to AI models, but many are still struggling to turn promise into value at scale. ​

​Technology has advanced to the point where it’s easy to produce a pilot, a prototype or a demo, but it's harder than ever to scale that pilot in production, to integrate, adopt and govern it so that it provides measurable impact to the business.​

That scalability gap is why forward deployed engineering (FDE) is becoming critical to successful enterprise AI implementation.

With FDE, highly skilled engineering team members are embedded within an organization’s product, operations and tech environments to work elbow-to-elbow with stakeholders. In my experience directing engineering teams at Deloitte, this can help accelerate delivery, shorten feedback loops and turn real-world business requirements into effective technical solutions.​

But proximity alone doesn’t optimize results. Technical expertise alone doesn’t do it either.

The true multiplier is industry context. For instance, teams that understand requirements like the Bank Secrecy Act and anti-money laundering obligations in financial services, or HIPAA and regulated electronic documentation requirements in life sciences and health care, are better prepared to build solutions that work in production.​​

Domain Fluency And Prioritization

The first job of any embedded team is deciding where to focus, and that’s where industry knowledge can be an advantage.

Teams with industry context can spot trapped value, friction points between handoffs, processes that limit growth and use cases that are large enough to affect value but not so broad that they get bogged down.

They can also differentiate a technically interesting project from one that will solve an actual business problem. So, prioritization is early and thorough, which can have a substantial impact on success. Translation of business concepts to technical reality also improves.

When engineers already understand the business model, turning business requirements into tangible outcomes is easier and iteration is faster.​

Risk Reduction With Industry-Awareness

It’s the same with generative AI and software delivery.

AI-powered development can automate manual tasks, augment drafting and testing and accelerate productivity. All these gains are real, but they can be difficult to realize without algorithms designed by engineers with industry-specific knowledge.

AI can also introduce issues with insecure code, inaccurate output and maintainability, all of which can increase technical debt when human review processes aren’t robust.

FDE teams with industry knowledge can reduce these risks because they can apply context-informed judgement on where to experiment, where operations may be affected and where strong quality checks are critical.

Conversely, productivity gains can increase with teams that have the industry context to challenge poor results and that use AI as an accelerator rather than a shortcut.​

Beyond Coding To Lifecycle Benefits

The potential benefits extend beyond simple code generation. The greatest value from generative AI extends across the full software development lifecycle.

Coding isn’t typically the biggest barrier to value realization. Instead, gaps between design and adoption or between technical elegance and business fit are often the biggest value killers.

FDE teams with industry skills and knowledge can help close those gaps. They understand the potential consequences that upstream decisions can have downstream for support models, data dependencies and user needs post-release.

That integrated view can help improve outcomes by enabling organizations to use AI where it improves the entire delivery chain, not just code generation.​

The Multiplier For Regulated Environments

The case for industry context becomes even more compelling for regulated environments. For example, financial services organizations must account for model risk, data privacy and auditability before moving solutions into production. As another example, life science and health care organizations must design for clinical workflows, strict data requirements and patient safety at the outset.

Industry-knowledgeable FDE teams can design within those constraints instead of retrofitting systems to them. That helps reduce rework, shorten approval cycles and prevent technically sound solutions from failing control reviews. The result is faster delivery, more credibility with stakeholders and greater trust in production systems.​

The Leadership Takeaway

If the goal is to increase value using a combination of embedded FDE teams and AI-augmented delivery, industry fluency must be an essential design requirement. If embedded teams create momentum and AI accelerates design and delivery, then industry context is the final element that converts those advantages into sustainable outcomes.

The improved use-case selection, better requirements-translation and enhanced risk management that come with using industry-skilled teams can result in solutions that provide real, lasting value. Organizations that deploy embedded FDE teams with industry knowledge are more likely to move beyond promising pilots toward tangible outcomes.​​

Forbes Technology Council is an invitation-only community for world-class CIOs, CTOs and technology executives. Do I qualify?