Articles for category: Delivery

February 3, 2022

Greg Thomas

Status Update Energy

I  heard this the other day from someone and can’t get it out of my mind – I call it SUE for short. SUE happens when someone enters a meeting and they are so pumped about what they are doing they rattle off status updates. We delivered this. I coded that. Someone is testing this. We are designing this tomorrow. This is good, status updates are good, but now give me the context of that delivery. Did we put in lots of Overtime to meet that delivery? Did we validate that last-second code? Does the team know what they are

February 1, 2022

Greg Thomas

Jumpers and Process

When I went to configure my first hard drive, I had to use my thick thumbs to put these tiny little jumper boxes into the back of the drive on the pins so that the computer would pick it up correctly. I’d try, reboot, try, reboot, and eventually, I’d get the message that the drive was detected and ready for use. Oh, happy days – I had done it, I had configured the drive correctly. That’s what building a new process is like, trying, rebooting, trying, rebooting, trying, rebooting – until eventually, it clicks with your team, you lock it

January 30, 2022

Greg Thomas

What are we Measuring?

If you don’t know what you are measuring, what the goal is, what matters in the end. What are you building for? How are you building it? And what will it be what you need when you get there? Knowing what you’re moving towards (and your team) is the most important part of your delivery. It might get repetitive as you ask the same questions over and over as your spidey sense tingles when you sense confusion is near.  But the more you ask, the more it will spurn others to ask as well. And if other’s are asking, then

January 28, 2022

Greg Thomas

Meeting Presets

Every meeting, whether it’s Zoom, Meet, or Teams – the same ritual occurs. Setup my layout the way I like it for meetings and presentations, do all the fiddling around. And then go. Why these presets cannot be saved, I’ll never know. Why functions I don’t need or have never used that need to be on, I’ll never know. If you’re throwing features against the wall hoping they’ll stick and no one is using them, you’re probably missing the point. The point being the user is having to clean up features from the floor just to make your product work.

January 26, 2022

Greg Thomas

Remotely Prepared: The Numbers are In

We knew this day would come, the numbers on how we are doing, what we are doing, where we are going and a glimpse into what be next. I love these reports, not entirely for the content, but for the conversations they generate. Findings from 2021: Work from Home Research Report

© 2025 Rambli by Greg Thomas. All rights reserved.