Lance HaigDec 4, 2024

Solution Engineers shape how customers experience your technology, yet traditional metrics miss what enables their success.

Drawing from my work with technical sales teams, I explore how measuring team satisfaction creates stronger customer outcomes. This is the first in a series examining practical implementation of the SPACE-SEA framework - a new approach to building highly effective Solution Engineering teams.

https://haigmail.com/measuring-satisfaction-and-well-being-in-solution-engineering/

#SolutionEngineering #Presales #management

Lance HaigDec 19, 2023

I found this article thanks to one of my colleagues to be very informative on being a technical / engineering manager in the current environment.

https://charity.wtf/2023/12/15/why-should-you-or-anyone-become-an-engineering-manager/
#management #solutionengineering

Becoming An Engineering Manager Can Make You Better At Life And Relationships

Original title: “Why Should You (Or Anyone) Become An Engineering Manager?” The first piece I ever wrote about engineering management, The Engineer/Manager Pendulum, was written as a lo…

charity.wtf
Nicolas Fränkel 🇪🇺🇺🇦🇬🇪May 17, 2023

Discuss the problem, not the solution https://blog.frankel.ch/discuss-problem-not-solution/

#solutionengineering #fromthearchives

Discuss the problem, not the solution

As a tech guy, I love to discuss technologies. And as discussions go, it’s generally the comparison kind: JVM vs. Net, Java vs. Kotlin, Go vs. Rust, Maven vs. the unspeakable one, etc. However, it’s too easy to fall into the quagmire of the merits and flaws of our beloved toys, talk about them for hours, and not reach a satisfactory agreement. A couple of years ago, I worked as a 'Solution Architect'. The job has different titles, e.g., Solution Designer, Solution Engineer, but the

A Java geek
Nicolas Fränkel 🇪🇺🇺🇦🇬🇪Apr 5, 2023

Discuss the problem, not the solution https://blog.frankel.ch/discuss-problem-not-solution/

#programming #engineering #solutionengineering #fromthearchives

Discuss the problem, not the solution

As a tech guy, I love to discuss technologies. And as discussions go, it’s generally the comparison kind: JVM vs. Net, Java vs. Kotlin, Go vs. Rust, Maven vs. the unspeakable one, etc. However, it’s too easy to fall into the quagmire of the merits and flaws of our beloved toys, talk about them for hours, and not reach a satisfactory agreement. A couple of years ago, I worked as a 'Solution Architect'. The job has different titles, e.g., Solution Designer, Solution Engineer, but the

A Java geek