Articles for category: Delivery

What’s In a Preview?

A new feature. A fix to an old bug. An idea for something new that you want to see whether there is some love from the market to keep it going? A direction you never thought of. A new platform of support. What should never be in a preview? Making your application harder to use then it was before. Putting your users through 5 clicks to accomplish a task that used to be done in one. Having to call support to fix an issue that wasn’t included in the preview and now they are stuck with. Cloud platforms are updated

June 24, 2020

Greg Thomas

Writing Features as Challenges

Whenever we write requirements, we start off with a great big vision that we want to achieve. This is great in theory but when people read it, especially if they are mid to end of the release and work is not going well, they instinctively push it aside for – “nice to haves”, “if we can get to it”, “maybe next sprint”. But if we switch our mindset and instead write our features as challenges we want to hit – we change our frame of reference to something we want to attain. Can we implement a chatbot for simple issues

June 23, 2020

Greg Thomas

It all comes down to Priorities

If you’re constantly forcing your team to hop between priorities and shiny objects, chances are your team will never get anything accomplished. Not for lack of trying but for lack of direction. The job of a leader is to keep the team’s eye on the goal, on the prize, on the delivery. Any external influences coming in are the Leader’s job to handle and keep off the team. And if you’re worried about your team not delivery enough “things”, remind people that they are instead focused on delivering that one “thing” that you wanted done right, correctly and the best

Lack of Leadership

A void in leadership can demotivate a team from 100 to 0 in seconds. Where everyone is looking for an answer, a path, a direction, anything that they can follow as a guide, hearing nothing in return leaves you feeling stuck, lost and confused. So what do you do? Step 1, figure out what you can do. Step 2, do it. Step 3, bring people in to so they can become a part of what you are doing. Step 4, don’t stop. Leadership appears in all sorts of places, even in ourselves, when we least expect it. Want more? Check

Today’s Summary…

It is okay to say to someone – you don’t need a summary for today’s meeting. Because you were there, in the moment, listening, taking feedback, asking questions, being a part of the conversation and listening to what everyone is saying. More than likely, you took your own notes. Summaries are for people who didn’t attend the meeting that need to know what was discussed. If you are leaving a meeting you just attended and need the summary to remember what was discussed and agreed upon, chances are… you didn’t attend the meeting. Want more? Check out my book Code