When the Demo Wins and the Requirements Lose
Why a scripted demo beats defined requirements, and what that costs later.
Read more
Book a Scoping Session From the practice / 01–03
Field Notes
Patterns, not case studies
About Field Notes
These are patterns, not case studies. Over eighteen years working inside engineering organizations, first as an electrical designer and later leading systems and automation work, I have watched the same failure modes repeat across different companies, different platforms, and different decades. Field Notes is where I write those patterns down.
You will not find client names, project timelines, or ROI figures here. What you will find is the diagnostic thinking behind the work: why a technically sound platform gets rejected in the boardroom, why the software rarely fails on its own, and where the real cost tends to hide before anyone can put a number on it. If a pattern sounds familiar, that recognition is the point.
As Glenn-Walker Systems Consulting takes on client engagements, this section will grow to include what we learn from that work as well.
The collection