Amit chakraborty

Posted on Nov 7 Originally published at amitchakraborty.dev

The forward-deployed engineer bootcamp · 2. The first customer meeting

#tutorial #career #theforward #identifyingtheactualproblem

The forward-deployed engineer bootcamp · Chapter 2 of 12 · Career · new chapter every Saturday morning

By the end of this chapter: Listen for the actual problem underneath the request.

The problem

You're a seasoned engineer considering a role as a forward-deployed engineer, and you've just landed your first customer meeting. You've prepared by researching the company and reviewing their technical stack, but as you sit down with the customer, you realize that their request - "we need to integrate your product with our existing system" - seems vague and open-ended. You're not sure what specific pain points they're trying to solve, or what their expectations are for the integration. You've been in situations like this before, where a poorly defined problem led to scope creep, delays, and ultimately, a dissatisfied customer. You know that you need to dig deeper to understand the actual problem underneath the request, but you're not sure how to ask the right questions or what to listen for.

You've spent hours preparing for this meeting, and you don't want to waste the opportunity. You know that if you can't accurately identify the customer's needs, you risk proposing a solution that won't meet their expectations, which could cost you the deal and damage your reputation. You need to be able to listen for the actual problem underneath the request, and ask the right questions to clarify their needs.

In your previous experience, you've seen how a poorly defined problem can lead to a 30% increase in project timelines and a 25% increase in costs. You've also seen how a well-defined problem can lead to a 20% reduction in project timelines and a 15% reduction in costs. You know that the key to success lies in being able to listen for the actual problem underneath the request, and you're determined to get it right this time.

Before you start

To get the most out of this chapter, you should have a basic understanding of the forward-deployed engineer role and its responsibilities, as covered in Chapter 1 of this series. You should also have experience working with customers and understanding their technical needs. Additionally, you should be familiar with common integration scenarios and the challenges that come with them.

To verify that you have the necessary prerequisites, try to answer the following questions:

What is the primary goal of a forward-deployed engineer?
What are some common challenges that come with integrating with a customer's existing system?
How do you currently approach customer meetings and identify their technical needs?

If you're unsure about any of these questions, review Chapter 1 and take some time to reflect on your experiences working with customers.

Understanding the customer's request

To listen for the actual problem underneath the request, you need to understand the customer's current pain points and what they're trying to achieve. This requires active listening and asking the right questions. Some key things to listen for include:

Specific examples of the problems they're experiencing
Their current workflow and how it's impacting their business
Their expectations for the integration and what they hope to achieve

Some questions you can ask to clarify their needs include:

Can you walk me through your current workflow and where you're experiencing pain points?
What are your goals for this integration, and how will you measure its success?
What are the key performance indicators (KPIs) that you're trying to improve?

Identifying the actual problem

Once you have a good understanding of the customer's request and their current pain points, you can start to identify the actual problem underneath the request. This may involve asking additional questions, doing some research, or seeking input from other stakeholders.

Some things to consider when identifying the actual problem include:

The customer's technical stack and how it may impact the integration
Any regulatory or compliance issues that need to be addressed
The potential risks and challenges associated with the integration

Build it

Here are the steps to follow to listen for the actual problem underneath the request:

Prepare for the meeting: Research the customer's company and review their technical stack. Review the meeting agenda and make sure you understand the purpose of the meeting.
Ask open-ended questions: Ask questions that encourage the customer to share their thoughts and feelings, such as "Can you walk me through your current workflow and where you're experiencing pain points?"
Listen actively: Pay attention to the customer's words, tone, and body language. Take notes and ask follow-up questions to clarify their needs.
Identify the actual problem: Based on the customer's input, identify the actual problem underneath the request. Consider the customer's technical stack, regulatory issues, and potential risks and challenges.
Verify your understanding: Verify your understanding of the customer's needs by summarizing what you've heard and asking for feedback.

When this breaks

Some common failures that can occur when trying to listen for the actual problem underneath the request include:

Misunderstanding the customer's needs: Failing to ask the right questions or not listening actively can lead to a misunderstanding of the customer's needs.
Failing to consider the technical stack: Not considering the customer's technical stack can lead to integration challenges and delays.
Not identifying potential risks and challenges: Failing to identify potential risks and challenges can lead to scope creep and delays.

To fix these failures, you can:

Go back to the customer and ask more questions: If you're unsure about the customer's needs, go back and ask more questions to clarify their requirements.
Research the customer's technical stack: Research the customer's technical stack to understand any potential integration challenges.
Develop a risk management plan: Develop a risk management plan to identify and mitigate potential risks and challenges.

What it costs

The approach outlined in this chapter requires a significant amount of time and effort upfront to understand the customer's needs and identify the actual problem underneath the request. However, this investment can pay off in the long run by reducing the risk of scope creep, delays, and dissatisfied customers.

Some potential trade-offs to consider include:

Time and effort: The approach outlined in this chapter requires a significant amount of time and effort upfront.
Cost: The approach may require additional resources and budget to research the customer's technical stack and develop a risk management plan.
Customer satisfaction: The approach may require more communication and collaboration with the customer, which can impact customer satisfaction if not managed effectively.

In the interview

In an interview for a forward-deployed engineer role, you may be asked questions like:

"Can you tell me about a time when you had to integrate with a customer's existing system? How did you approach the project?"
"How do you ensure that you understand the customer's needs and identify the actual problem underneath the request?"
"What are some common challenges that you've experienced when integrating with a customer's existing system, and how have you overcome them?"

A weak answer might focus on the technical details of the integration, without considering the customer's needs and the actual problem underneath the request. A strong answer would highlight the importance of understanding the customer's needs, identifying the actual problem, and developing a risk management plan to mitigate potential risks and challenges.

For example, a strong answer might sound like:

"In my previous role, I worked on a project where we had to integrate with a customer's existing system. I started by researching the customer's technical stack and reviewing their current workflow. I then met with the customer to understand their needs and identify the actual problem underneath the request. Based on our discussion, I developed a risk management plan to mitigate potential risks and challenges. The project was successful, and the customer was satisfied with the outcome."

As you progress in your career, the questions you'll be asked in an interview will change. As a junior forward-deployed engineer, you might be asked to describe your experience with integration projects and how you approach customer meetings. As a senior forward-deployed engineer, you might be asked to discuss your approach to risk management and how you prioritize customer needs. As a director or engineering manager, you might be asked to discuss your strategy for scaling the forward-deployed engineer function and how you measure its effectiveness.

Your tasks

Research a company's technical stack: Choose a company and research their technical stack. Identify potential integration challenges and develop a plan to mitigate them.
Conduct a mock customer meeting: Conduct a mock customer meeting with a colleague or friend. Practice asking open-ended questions and listening actively to understand the customer's needs.
Develop a risk management plan: Develop a risk management plan for a hypothetical integration project. Identify potential risks and challenges, and outline a plan to mitigate them.
Reflect on a past project: Reflect on a past project where you had to integrate with a customer's existing system. What did you do well, and what would you do differently next time?
Create a checklist for customer meetings: Create a checklist for customer meetings that includes questions to ask and things to listen for. Use this checklist to prepare for your next customer meeting.

Your tasks this week

Do the exercises above before the next chapter. Reading a tutorial and doing
one are different activities and only one of them changes what you can build.

Stuck on any of them? Say so — describe what you tried and what happened:
tell me where you got stuck. I read every one, and the questions
that come back more than twice get answered in the next chapter.