Articles for category: Delivery

March 12, 2020

Greg Thomas

Escalating Confusion

The scariest thing I see in any software delivery team is confusion. Running out of licenses? That can be fixed. Not sure what development platform to use? You’ll figure it out. The User Interface looks like garbage? We can buff it out. The app is too slow? We can make it faster. But when the team is confused, when the team doesn’t know what they should be doing, or what direction they should be headed? That’s scary, everything else can be triaged, managed or handled. But you can’t triage confusion, you can’t manage it and the only way to handle

March 11, 2020

Greg Thomas

Find your Release Anchor

Anchors are big, heavy pieces of metal that you drop out of a boat when you’re close to land so your boat doesn’t drift away. They keep you in one spot. Too often in a release, where we started is not where we end up. What was originally meant to be the release, is no longer the release and what we are shipping is something vastly different than what was originally intended. For this reason, releases need to have anchors. They need to have that connection to what was intended when the idea for the release was conceived. They need

March 6, 2020

Greg Thomas

Code Your Way Up is Available Today

Aka – the Neverending Project. If you’ve been reading what I’ve been putting out over the past few years or engaged in some conversations on topics of software and leadership, I have good news – I finally finished the neverending project. Code Your Way Up is available today for purchase as an eBook or Paperback on Amazon (CAN and US). Full details are available here on all the going ons and how to stay in the loop post-launch but most importantly, I would love to hear from those that read it, what are your thoughts, what resonates, what’s good, etc,

March 5, 2020

Greg Thomas

Out of Date Content

There is a trend happening in software where the documentation cannot keep up. It’s a problem that cannot be solved by AI or technology. With development cycles shrinking to bi-yearly to quarterly, what was written in Q1 about a new piece of software could be outdated by Q3. Even worse, for the developer trying to get a blog off the ground, their content could be invalidated within 2 months of going live. Just today, I was sent a blog from an organization on how to implement a new feature that was written almost a little over a year ago and

© 2025 Rambli by Greg Thomas. All rights reserved.