One of the topics I often hear from friends and colleagues a like is that they always struggle with 1:1’s with their leader or direct reports. Usually, it ends in some kind of casual conversation which leaves both parties craving for more and feeling like the meeting was not really focused. In a climate where our time is precious and the “meeting” culture of home office has increasing pressure on our schedules, we need to really focus on value proposition when it comes to these regular sync meetings.

I decided to experiment, by focusing the meeting on a semi-structured approach…


When the first Remarkable Tablet launched, I was watching closely. Being someone who loves the analog feeling of notepad and pen but also someone who loves to be a digital native, it seemed like a great mix of both worlds. The design felt a little lacking in the first one and from what I heard from the early experience, it was lacking some must have functionality in the software experience (especially syncing).

During the same period, I got into the wonderful world of iPad Pro computing, a all in one multi functional machine which when you let it, can reshape…


The 2:1 Method is an easy approach I utilise at home to reduce stress and make sure I never run out of essential items. It’s super simple, every item which is essential and would annoy me if we ran out of, I buy two of them and once the first item is empty, finished or no longer functioning I then add it to my shopping list for the next time I’m shopping.


One of the common issues I’ve witnessed during the many years of being a part of software development is the way we handle and classify not only bugs but also all tickets. We are now living and breathing agile and I think we need to adopt a much smoother, transparent and efficient way of classifying tickets.

Ingredients

  • Jira or your favourite ticketing system

So, where are we now?

At the moment I see a somewhat of a common trend when speaking with others within the software development field (mostly the video game sector) as well as my own personal experience of 11+ years in the Games…


Cycle Times present really interesting insights into how your team is Jira delivering and can highlight any potential bottlenecks in the flowprocess as well as serving as good benchmark for the team.

Additional Insights

If you want further insights into Lead Time and Cycle Time. you should look into: https://kanbanize.com/kanban-resources/kanban-software/kanban-lead-cycle-time

Ingredients

  • Jira

Cycle Time with Jira Reports

Jira comes with a report type called “Control Chart” which is used to see a boards cycle time and to get an overview based on a timeline how all of the tickets have been progressing.

Here is an example of how a Control Chart looks like:


The Jira Backlog Health Report is a nice and simple tool that can help generate insights into your own backlog. The tooling can be used to also ask questions such as all the tickets that were last touched (updated) more than 12 weeks ago, is it still relevant?

Ingredients

  • Jira
  • a Dashboard
  • a Filter

Prerequisites

Below are two prerequisites for this Backlog Health Report:

  • A Jira Dashboard
  • A Jira Filter saved that already shows “all” issues for your team, this can be achieved by just saving a filter with the component for your team selected.

You can copy and paste the below…


I really like the Eisenhower Matrix and it’s a tool I use a lot to help declutter my todo list and to be able to really focus on what matters. As I was mainly using Todoist as my personal todo list application of choice, I wanted to create a simple yet affective system with the Eisenhower Matrix at its core.

More details on the Eisenhower Matrix: https://www.eisenhower.me/eisenhower-matrix/

Ingredients

  • Todoist

The approach I take to the tooling set-up is to adapt it to function as the Eisenhower Method teaches. I like the Eisenhower Method as it better fits my own judgement and…


One of the tools I’ve always got in my back pocket which suits almost all occasions is mind-mapping. This versatile tool and approach is a quick and easy way to break up a problem or pain point, find out new items to work on and to also plan out bigger topics. One of the fundamental benefits of the tool is that it enables all participants to gain a new perspective. Instead of viewing topics head on, you’re somewhat removed from the situation and placed in a birds-eye view. …


A lot of time and energy is invested in discussions around decisions. One of the ways in which you can minimise discussions is to have a Lightning Decision Jam around a topic to make sure the discussions are focused on where the most value will be generated.

Personally I have used thus to help define team’s roadmaps for the coming half year or quarter. But you can also use such a method for a varied amount of situations.

Ingredients

  • In Person
  • Sticky Notes
  • Small Dot Stickers
  • Pens
  • Virtual
  • Jamboard
  • EasyRetro

What is an LDJ (Lightning Decision Jam)?

An LDJ is a lightweight and simple way for a team…


The technique has been borrowed from Philip Rosedale‘s interview with Kevin Rose on the Foundation Video Series (YouTube) in the interview Philip mentioned a technique he always did as CEO to gauge feedback and to gauge a trend line, on a very frequent basis he would send a survey out to all the employees asking them three simple questions:

  • One a scale of 1–5 (1 being really bad and 5 being really good) how well am I doing at my job right now?
  • What was the key motivation for giving me that rating?
  • Is there anything I can improve on?

Ingredients

Joseph Hill

I love to travel (10+ countries and counting) and meet new people. I am totally into productivity and the tooling around it, as well as the start-up scenes

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store