Originally published at http://tomek.kaczanowscy.pl on September 26, 2020.
You organize an event. Let’s say an internal one, like all-hands meeting, a workshop, or something else for the teams you work with. After wards you send around a feedback form. You get the answers and now you plan to analyse what people told you so that you can improve the next time.
Well, that was a no-brainer. That is what we all do.
But there is one more thing that you should consider doing. Right after you receive feedback publish all of it to all participants.
There are few reasons for…
Originally published at http://tomek.kaczanowscy.pl on September 6, 2020.
Ever heard of the sandwich feedback method? Basically, it boils to this:
A) first you say something nice ( “I like / appreciate that you do [whatever]”),
B) then you say what you really wanted to say — so called “corrective feedback” ( “you did [whatever] and that is why we had such and such issues, so better never do [whatever] again”, etc. etc.),
C) then you say something nice again.
The idea is that maybe it is easier to swallow this bitter pill if you wrap it in sugar. …
Originally published at http://tomek.kaczanowscy.pl on July 14, 2020.
There is a long-time debate if you should re-estimate user stories that you haven’t finished during a sprint. My answer is:
yes, you should!
And this is why.
First of all, let me explain what I use estimates and story points for. Mostly so it is easier to decide how much the team is able to deliver during a sprint. If you have some historical date as to your capacity, then it is easier to decide whether you will be able to deliver X or only half of it. …
Originaly published at http://tomek.kaczanowscy.pl/2020/04/recruitment-lessons-learned/
First, let me give you some context. I’m an IT leader with ~15 years of software development experience. Recently I was looking for a new job, which was something I haven’t done in 10 years or more (and when I did, I was junior Java dev, so it was totally different). So in the last 3 months I’ve learned a lot. And since nowadays many people — even in the IT dreamland — are looking for a job, maybe my experiences and lessons learned will be of some value.
FYI, I have started my recruitment journey…
This article was first published at http://tomek.kaczanowscy.pl/2020/02/review-early-review-often/
I got a review of the first sections of my new (work-in-progress) book. Hurray!
It is hard to admit but some part of me foolishly expected that reviewers — Jakub Nabrdalik & Karolina Hałaszkiewicz — would congratulate me on a good job rather than report what is wrong with it. How silly of me! :) Yes, of course, they found issues, in fact, many issues, and I have to admit some very serious ones. (And — have no doubts about it — I’m very grateful for every single comment I received!)
This articles was first published at http://tomek.kaczanowscy.pl/2020/02/lessons-in-bathroom-cleaning/
TLDR: Developing software is like cleaning bathrooms. Or should be.
Yesterday I spent some time in a nice coffee bar. I had a coffee there, worked a little, enjoyed the music and the murmur of talks around me, and also, I visited the bathroom. It was clean. Maybe not super-shiny, White Glove Test level clean, but clean enough to use it without any distaste. And this cleanness encouraged me to leave the bathroom in the same good shape as I’ve found it. …
This articles was first published at: http://tomek.kaczanowscy.pl/2020/03/so-you-have-a-plan-huh/
Yesterday during a group workshop there was a task to facilitate. It seemed pretty simple to me. “Piece of cake”, I said to myself, and I volunteered to facilitate this session.
I’ve seen it being done before, and I was sure I am up to the job. I quickly came with a plan. It was a good plan. First, we do this, then that, and then this and this and ta-da! we’ll have it. I had it all figured out.
And then I started facilitating. In the beginning, all went well. I had…
This post was originally published at http://tomek.kaczanowscy.pl/2019/06/angry-user-ux-rant-part-1/
Sometimes I get pretty annoyed by UX of various software I use. In this post I gathered few examples of things that would benefit from some more thoughtful UX approach.
I named this post “Part 1” as I imagine I will have few more rants in the future! :)
To close a popup window using mouse / touchpad you need to:
What is faster? Keyboard is faster! You hit ESC and voila! …
This blog post opens a series devoted to 4DX (4 Disciplines of Execution) framework (see here for all posts).
Basically, the 4DX helps to achieve team’s priority in the midst of urgency. It consists of 4 steps which I describe below. For details, I suggest you check the book.
First thing you need to decide what is your priority (remember, priority is singular, not plural!). Then, you should express it in the form of:
“from [initial value] to [desired value] by [deadline]”
so you know:
This post was originally published at http://tomek.kaczanowscy.pl/2019/05/4dx-lag-vs-lead/
This blog post is based on my experience with 4DX (4 Disciplines of Execution) framework (check their book or wait till I write more posts about it). I will go with a simple example to introduce the concepts of LAG and LEAD measures, which are an important part of 4DX.
[Disclaimer] I have heard at least 3 naming variants. Some people refer to LAG/LEAD metrics, some to measures and some call them indicators. Personally, I don’t give a damn. The concept works for me, and that is enough.
Imagine you want to beat…