Articles and Posts

Allowing exceptions for gifted brilliance, my firm belief is that leadership should be earned through toil at craft.

On my third iteration of paper prototype mainly working with one power user. Time to share with more users…

Prototying export to word feature in Balsamiq and then realized, why am I just building it in Word itself? #pickheadup #doh

#ReasonsWhyAgileFails: 1) Seen as just a means to make developers produce exactly the same low value work they were doing before only faster

#ReasonsWhyAgileFails: 3) Leaders don’t actually remove obstacles or allow the teams to self-organize

#ReasonsWhyAgileFails: 4) people don’t actually do the practices but just rebrand their existing habits “agile”

#ReasonsWhyAgileFails: 2) Focus on scaling up before anyone in the organization has internalized any of the values and practices

#ReasonsWhyAgileFails: 5) Quitting during the early, conflict ridden stages before realizing any benefits because, “It’s not working

Using Jeff Patton story mapping book as external conscience to spend time with users, prototype in multiple rounds, remain open to change.

Setting up node and angular on suggestion it may be our way to build rich web apps within windows infrastructure.

As a software developer, walking through a paper prototype with a prospective power user is exhilarating.

What brings me joy in my work? Mutual loyalty, comraderie, human scale and something interesting to make.