Less hectic, more impactful, on-time software

Here are some questions I’ve received when presenting the Constraint Anchor term.

It’s been great to talk through this several times with others. Also, I’ve appreciated all the questions, feedback and wondering.

I’m paraphrasing to be concise, but here they are:

“Aren’t there more than just Planning and Delivery?”

Yes, there are more categories of work besides just Planning and Delivery, but I see the other categories being inside of Planning and Delivery.

A couple of days ago, I brought up the team’s constraint concept: a binary focus between planning and delivery.

This reminded me of the Sailboat Exercise we’ve done at Sodium Halogen. The sailboat exercise has the team brainstorm two categories about how the team is doing: the wind, anything that pushes the team forward, and the anchor(s), anything that slows the team down.

An anchor has two hooks: the left and right. ⚓ When the anchor is thrown off the sailboat, one side of the anchor drags and catches the seabed and slows the vessel down.

When I have AI generate with little direction from me, I feel what gets created is foreign to me or unappealing.

Really, I have little sense of ownership with what was generated.

What AI creates feels very much like a guest room.

I didn’t create the furniture in the guest room, but I also didn’t have any choice in the matter of how the furniture was placed or the decorations that were added. This just doesn’t feel like home.