You've determined the scope of the problem your lasagna strategy is intending to solve, now you uncovered different bits of info:

  • It's 3pm and lasagna takes at least 2 hours
  • There are no tomatoes at home
  • Can't shorten the recipe
  • It's Carla's birthday
  • She expects us to do something
  • Carla loves lasagna
  • She leaves tomorrow
  • Can't make lasagna without tomatoes
  • She will be disappointed if we don't make lasagna
  • We need something tonight

The problem is that this information isn't yet sorted – you and your partner were having a conversation about lasagna, asking questions, throwing out ideas, and all this is now laid out on the proverbial table.

How do you sort them into fact or fiction? Identify which ones are assumptions and validate them.

For example, is "Can't shorten the recipe" fact or fiction? What if you could skip a step? Get something premade to speed it up? If it was said without actually checking the recipe, it's an assumption that needs to be validated.

Assumptions are guilty until proven innocent.

Being able to uncover and identify facts and validate assumptions is a superpower – because it allows you to help solve the situation more creatively.

We make assumptions ALL THE TIME. And yet, we don't validate as often as we should (including our own).

What are the assumptions underlying your current DevEd strategy? Have you identified them, shone a light on them, and put them under a microscope?

Have a lovely day,

Assumptions are guilty until proven innocent

Want devs to love your product?

Hi 👋 I'm Kamran. I'm a consulting developer educator who can help your DevRel team increase adoption with better docs, samples, and courseware.
Sign up