𝗧𝗵𝗲 𝗠𝗼𝘀𝘁 𝗘𝘅𝗽𝗲𝗻𝘀𝗶𝘃𝗲 𝗗𝗲𝗰𝗶𝘀𝗶𝗼𝗻 𝗮𝗻 𝗙𝗗𝗘 𝗖𝗮𝗻 𝗠𝗮𝗸𝗲

𝗠𝗼𝘀𝘁 𝗙𝗗𝗘𝘀 𝘄𝗶𝗹𝗹 𝗳𝗮𝗰𝗲 𝘁𝗵𝗶𝘀 𝗱𝗲𝗰𝗶𝘀𝗶𝗼𝗻. 𝗙𝗲𝘄 𝘄𝗶𝗹𝗹 𝗮𝗴𝗿𝗲𝗲 𝗼𝗻 𝘁𝗵𝗲 𝗿𝗶𝗴𝗵𝘁 𝗮𝗻𝘀𝘄𝗲𝗿.

You're 3 weeks into a customer deployment.

The customer suddenly asks for a feature that wasn't in scope.

It's technically possible...

But building it will:

• Delay the deployment by two weeks.

• Create technical debt your product team will eventually inherit.

• Make the customer incredibly happy.

• Set a precedent they'll expect forever.

You have exactly 1 hour before your meeting with the customer.

𝗬𝗼𝘂 𝗰𝗮𝗻 𝗼𝗻𝗹𝘆 𝗰𝗵𝗼𝗼𝘀𝗲 𝗼𝗻𝗲.

🟢 𝗢𝗽𝘁𝗶𝗼𝗻 𝗔 — Build it.

🔵 𝗢𝗽𝘁𝗶𝗼𝗻 𝗕 — Push back and explain why.

🟣 𝗢𝗽𝘁𝗶𝗼𝗻 𝗖 — Find a completely different solution.

𝗛𝗲𝗿𝗲'𝘀 𝘁𝗵𝗲 𝗶𝗻𝘁𝗲𝗿𝗲𝘀𝘁𝗶𝗻𝗴 𝗽𝗮𝗿𝘁.

There isn't a correct answer.

The best FDEs aren't defined by how much they build.

They're defined by how they make tradeoffs under uncertainty.

So here's the challenge:

𝗗𝗼𝗻'𝘁 𝘁𝗲𝗹𝗹 𝘂𝘀 𝘄𝗵𝗮𝘁 𝘆𝗼𝘂 𝘁𝗵𝗶𝗻𝗸.

Tell us what you would actually do.

Reply using this format:

① 𝗬𝗼𝘂𝗿 𝗰𝗵𝗼𝗶𝗰𝗲 (A, B, or C)

② 𝗧𝗵𝗲 𝗳𝗶𝗿𝘀𝘁 𝘀𝗲𝗻𝘁𝗲𝗻𝗰𝗲 𝘆𝗼𝘂'𝗱 𝘀𝗮𝘆 𝘁𝗼 𝘁𝗵𝗲 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿

③ 𝗧𝗵𝗲 𝗯𝗶𝗴𝗴𝗲𝘀𝘁 𝗿𝗶𝘀𝗸 𝘆𝗼𝘂'𝗿𝗲 𝗮𝗰𝗰𝗲𝗽𝘁𝗶𝗻𝗴

④ 𝗦𝗶𝘅 𝗺𝗼𝗻𝘁𝗵𝘀 𝗹𝗮𝘁𝗲𝗿... 𝘄𝗵𝗮𝘁 𝗱𝗼 𝘆𝗼𝘂 𝘁𝗵𝗶𝗻𝗸 𝗵𝗮𝗽𝗽𝗲𝗻𝘀?

I'm especially curious about something:

Have you ever made the wrong decision in a similar situation?

Not because you lacked technical skills...

But because you misjudged the people, incentives, or long-term consequences.

Those stories are often more valuable than success stories.

👇 𝗗𝗿𝗼𝗽 𝘆𝗼𝘂𝗿 𝗮𝗻𝘀𝘄𝗲𝗿 𝗯𝗲𝗹𝗼𝘄.

Then read someone else's response and tell them what you would have done differently.

Let's compare decision-making not just outcomes.

1 comment

𝗧𝗵𝗲 𝗠𝗼𝘀𝘁 𝗘𝘅𝗽𝗲𝗻𝘀𝗶𝘃𝗲 𝗗𝗲𝗰𝗶𝘀𝗶𝗼𝗻 𝗮𝗻 𝗙𝗗𝗘 𝗖𝗮𝗻 𝗠𝗮𝗸𝗲

skool.com/fde

Build, deploy, and grow as forward deployed engineers solving real-world AI and enterprise problems with impact.

Leaderboard (30-day)