TRASCRIZIONE 🔗
WEBVTT
00:00:00.000 --> 00:00:03.040
There's an old trick for getting kids to eat
00:00:03.040 --> 00:00:06.299
their vegetables. You hide them in a fruit smoothie.
00:00:06.599 --> 00:00:09.539
They get the good stuff, and they're too busy
00:00:09.539 --> 00:00:13.660
having fun to notice. My guest today does that
00:00:13.660 --> 00:00:16.960
with engineering retrospectives. She turns them
00:00:16.960 --> 00:00:20.859
into a tabletop role-playing game, with characters,
00:00:21.120 --> 00:00:24.800
chapters, and a story built around what her team
00:00:24.800 --> 00:00:28.839
went through. Her point is that silliness disarms
00:00:28.839 --> 00:00:32.000
people, and that's when you get honest answers.
00:00:32.380 --> 00:00:35.759
Hand an engineer an orc to play, and they might
00:00:35.759 --> 00:00:38.859
say the thing they'd never put on a retro board.
00:00:39.340 --> 00:00:42.399
It's not really how they feel. They're just an
00:00:42.399 --> 00:00:45.100
orc. I'm Brian Teller from Teller's Tech, and
00:00:45.100 --> 00:01:04.780
this is Ship It Weekly. Welcome back to Ship
00:01:04.780 --> 00:01:07.379
It Weekly, where I filter the noise and focus
00:01:07.379 --> 00:01:09.599
on what matters when you are the one running
00:01:09.599 --> 00:01:13.140
infrastructure and owning reliability. Most weeks,
00:01:13.260 --> 00:01:17.900
it's a quick DevOps, SRE, platform, cloud, and
00:01:17.900 --> 00:01:21.599
security news recap. In between those, I do conversation
00:01:21.599 --> 00:01:25.200
episodes with people building and operating these
00:01:25.200 --> 00:01:29.060
systems. Ship It Weekly turns one this November.
00:01:29.299 --> 00:01:32.519
To celebrate, through mid-December, you're getting
00:01:32.519 --> 00:01:36.120
two conversations a week, Mondays and Wednesdays,
00:01:36.120 --> 00:01:39.659
with the news every Friday. Then, we're back
00:01:39.659 --> 00:01:43.170
to our usual rhythm. Today, I'm joined by Jinger
00:01:43.170 --> 00:01:46.450
Meilani, Senior Software Engineer in DevOps at
00:01:46.450 --> 00:01:49.890
Mountain, and the creator of something she calls
00:01:49.890 --> 00:01:53.670
Tabletop Retro. It's a good one for Halloween
00:01:53.670 --> 00:01:56.989
week too, because this whole thing started as
00:01:56.989 --> 00:02:01.030
a spooky retro she ran around Halloween. We talk
00:02:01.030 --> 00:02:05.549
about why she calls it retro plus plus plus, how she builds
00:02:05.549 --> 00:02:08.710
one out of chapters, characters, and technical
00:02:08.710 --> 00:02:12.159
archetypes, why playing a character helps some
00:02:12.159 --> 00:02:15.800
people speak up and makes others nervous, and
00:02:15.800 --> 00:02:19.419
how to run a lightweight one of your own without
00:02:19.419 --> 00:02:23.199
building a whole fantasy world. All right, let's
00:02:23.199 --> 00:02:29.879
jump in. Jinger, thank you for joining me. Thank
00:02:29.879 --> 00:02:31.780
you so much for having me. I'm super excited
00:02:31.780 --> 00:02:35.039
to talk about this because it is just the accumulation
00:02:35.039 --> 00:02:37.879
of so many things I love, which is world building,
00:02:38.039 --> 00:02:41.020
psychological safety in teams, and engineering
00:02:41.020 --> 00:02:44.539
enablement. So it really hits a particular niche
00:02:44.539 --> 00:02:47.120
that I feel very well qualified to talk about.
00:02:47.419 --> 00:02:49.560
Okay, let's start there. Why reinvent the retro?
00:02:50.539 --> 00:02:52.620
Personally, to be honest, it's because I was
00:02:52.620 --> 00:02:55.900
bored of them. Even when I would try to do a
00:02:55.900 --> 00:02:58.340
more fun retro, right? There are some that kind
00:02:58.340 --> 00:03:02.020
of have a visual spin or a metaphor kind of embedded
00:03:02.020 --> 00:03:05.360
in there. And even those, you know, they kind
00:03:05.360 --> 00:03:08.979
of get rote. And honestly, like, especially remote,
00:03:09.080 --> 00:03:11.460
if you don't have cameras on, I am tuning out.
00:03:11.539 --> 00:03:14.050
I'm not. I'm not engaged. I'm not really thinking
00:03:14.050 --> 00:03:16.729
about it. Sometimes I can't remember, you know,
00:03:16.750 --> 00:03:19.789
what I did yesterday, much less, you know, what
00:03:19.789 --> 00:03:22.189
I did two weeks ago and then all of that time.
00:03:22.310 --> 00:03:26.050
So when one of the previous companies I was at,
00:03:26.150 --> 00:03:29.870
we would rotate through who did the retros. And
00:03:29.870 --> 00:03:33.930
because I love Halloween, I love the Halloween
00:03:33.930 --> 00:03:36.069
season, and I love taking things way too far,
00:03:36.169 --> 00:03:39.939
again, with narratives and themes. It was my
00:03:39.939 --> 00:03:42.199
time right where it lined up around Halloween.
00:03:42.319 --> 00:03:46.240
So I decided to just kind of build a story around
00:03:46.240 --> 00:03:48.800
our team. It wasn't anything super grandiose,
00:03:48.800 --> 00:03:51.120
but over time, as I continue to do it throughout
00:03:51.120 --> 00:03:52.539
the years and continue to do it with different
00:03:52.539 --> 00:03:56.219
teams, I do it annually. So every year I get
00:03:56.219 --> 00:03:59.639
a little bit more heavily involved. What's different
00:03:59.639 --> 00:04:03.639
about this tabletop format, though? What are
00:04:03.639 --> 00:04:07.900
we diving into? What are you pulling out of people that maybe
00:04:07.900 --> 00:04:09.740
you aren't pulling out of at a normal retro?
00:04:10.319 --> 00:04:13.120
Yeah, for sure. First of all, Tabletop Retro
00:04:13.120 --> 00:04:15.979
isn't, I wouldn't necessarily even call it a
00:04:15.979 --> 00:04:18.319
replacement for the standard retro. I would call
00:04:18.319 --> 00:04:21.319
it retro plus, plus, plus. So all of these formats
00:04:21.319 --> 00:04:25.279
that you know and love are still viable and they're
00:04:25.279 --> 00:04:27.199
still feasible within this entire story that
00:04:27.199 -->
Load full transcript
00:04:29.899
we're building. And that's part of what you get
00:04:29.899 --> 00:04:32.959
out of Tabletop Retro, just right up front is
00:04:32.959 --> 00:04:36.019
the entire retrospective, however long you decide
00:04:36.019 --> 00:04:39.439
to run your campaign for, is not one activity.
00:04:39.699 --> 00:04:43.399
It is a bunch of activities and it's an uncovering
00:04:43.399 --> 00:04:46.720
of not even just the story that the lead has
00:04:46.720 --> 00:04:49.259
created for everybody, but also the uncovering
00:04:49.259 --> 00:04:52.459
of a lot of emotional elements that, you know,
00:04:52.459 --> 00:04:56.620
are very easily missed in a regular typical retrospective
00:04:56.620 --> 00:05:00.750
because it's not creating that environment for
00:05:00.750 --> 00:05:03.110
people to really dive in and experience something,
00:05:03.269 --> 00:05:05.850
right? It's just kind of saying like, okay, let's
00:05:05.850 --> 00:05:09.250
attempt to introspect, but I will not set the
00:05:09.250 --> 00:05:12.569
scene for you. I will not remind you of what's
00:05:12.569 --> 00:05:15.350
really has happened. And I will not do anything
00:05:15.350 --> 00:05:20.410
that pushes your mind to get excited. And so
00:05:20.410 --> 00:05:24.490
those elements primarily, I wanted to... Not
00:05:24.490 --> 00:05:27.029
fix. Fix isn't the right word. I wanted to do
00:05:27.029 --> 00:05:29.490
something about that while still getting all
00:05:29.490 --> 00:05:32.589
of the goodness that comes out of a retrospective,
00:05:32.589 --> 00:05:35.769
right? Things like we understood what we did.
00:05:36.129 --> 00:05:38.870
We know what we want to do better. We understand
00:05:38.870 --> 00:05:41.850
the posture of the team. We know where we're
00:05:41.850 --> 00:05:44.790
aligned and unaligned. All of those things are
00:05:44.790 --> 00:05:46.889
still the foundation of Tabletop Retro, just
00:05:46.889 --> 00:05:49.170
like they are for any other retrospective. And
00:05:49.170 --> 00:05:51.170
you mentioned you don't do these for every retro.
00:05:51.290 --> 00:05:54.939
What cadence would you recommend for? for a tabletop
00:05:54.939 --> 00:05:59.879
retro? Yeah, it's heavily dependent on the amount
00:05:59.879 --> 00:06:03.939
of complexity and storytelling that you want
00:06:03.939 --> 00:06:07.540
to do, the amount that you want to put out in
00:06:07.540 --> 00:06:10.560
there, I would say. So I like to do it annually.
00:06:10.639 --> 00:06:13.740
Like I said, I like to make it spooky. So I do
00:06:13.740 --> 00:06:16.360
kind of a spooky retro variant. And I like an
00:06:16.360 --> 00:06:20.850
annual story because it allows me to not... One,
00:06:20.870 --> 00:06:23.110
always be thinking about Tabletop Retro, like
00:06:23.110 --> 00:06:25.529
I get to do my own work, right? I'm not constantly
00:06:25.529 --> 00:06:28.050
thinking about how to build this world. You can
00:06:28.050 --> 00:06:31.689
be strategic about, you know, how, not how often
00:06:31.689 --> 00:06:33.610
it happens, but when in the year it'll happen.
00:06:33.670 --> 00:06:36.670
I wouldn't recommend doing something this involved,
00:06:37.089 --> 00:06:39.149
something where you want people to put a lot
00:06:39.149 --> 00:06:42.629
of themselves into when there is something huge
00:06:42.629 --> 00:06:45.509
happening, right? We have fires every day. Let's
00:06:45.509 --> 00:06:47.970
not play games right now. Let's, you know, unless
00:06:47.970 --> 00:06:50.339
it's... We can have quick conversations kind
00:06:50.339 --> 00:06:51.959
of about like, why are we having these fires?
00:06:52.060 --> 00:06:54.000
But I don't think that's the appropriate moment
00:06:54.000 --> 00:06:57.220
to then try to take fire as a metaphor and say,
00:06:57.319 --> 00:06:59.699
you know, we are fighting a flame-breathing dragon.
00:06:59.860 --> 00:07:02.339
I think that can happen after, you know, things
00:07:02.339 --> 00:07:04.519
have sort of settled. And it also leads into
00:07:04.519 --> 00:07:07.040
the idea that people have to be comfortable in
00:07:07.040 --> 00:07:10.279
order to speak their truth, in order to tell
00:07:10.279 --> 00:07:13.379
you things honestly. When there's a lot going
00:07:13.379 --> 00:07:15.339
on and people are already stretched thin, I don't
00:07:15.339 --> 00:07:17.360
think that's the most comfortable situation to
00:07:17.360 --> 00:07:20.120
put a team in. Yeah, that's fair. So I was trying
00:07:20.120 --> 00:07:23.399
to reconcile this. So it's less about like a
00:07:23.399 --> 00:07:27.199
blameless culture or like talking about issues
00:07:27.199 --> 00:07:30.800
during the last sprint or whatever, you know,
00:07:30.800 --> 00:07:33.500
whatever the retro is for. And it's more about
00:07:33.500 --> 00:07:36.759
like keeping it less dry or do they both go hand
00:07:36.759 --> 00:07:39.740
in hand? Like what is the primary purpose of
00:07:39.740 --> 00:07:42.480
the tabletop for the engineers? Like what are
00:07:42.480 --> 00:07:44.500
they going to get out of it? And along those
00:07:44.500 --> 00:07:47.259
same lines, do you find more frank conversations
00:07:47.259 --> 00:07:51.100
or revelations from that than you would like
00:07:51.100 --> 00:07:55.060
a traditional retro? Right, right. I would definitely
00:07:55.060 --> 00:07:57.600
say that they kind of play off each other. And
00:07:57.600 --> 00:08:00.759
the element of psychological safety and honesty
00:08:00.759 --> 00:08:03.899
also kind of come into play here. I will throw
00:08:03.899 --> 00:08:06.579
in kind of a fifth element, which is silliness.
00:08:06.660 --> 00:08:10.000
So it's this accumulation of like, I want to
00:08:10.000 --> 00:08:13.209
disarm you, right? That disarmament allows you
00:08:13.209 --> 00:08:16.250
to fully embody the situation, right? I kind
00:08:16.250 --> 00:08:18.790
of use this metaphor of like hiding vegetables
00:08:18.790 --> 00:08:22.029
in a
fruit smoothie, right? I get a lot of honest
00:08:22.029 --> 00:08:25.069
answers without people necessarily understanding
00:08:25.069 --> 00:08:27.269
me, but they're giving me an honest answer, right?
00:08:27.350 --> 00:08:29.649
Because sometimes the metaphors work out really
00:08:29.649 --> 00:08:31.310
well or the mappings work out really well where
00:08:31.310 --> 00:08:33.809
we all kind of think we're talking about one
00:08:33.809 --> 00:08:35.629
thing when secretly we're talking about another
00:08:35.629 --> 00:08:38.090
thing and these dynamics kind of hold, right?
00:08:38.620 --> 00:08:40.700
Whether we're playing a game or whether we have
00:08:40.700 --> 00:08:43.440
to collaborate together as a team. So there's
00:08:43.440 --> 00:08:47.120
definitely the engagement sort of unlocks things
00:08:47.120 --> 00:08:49.899
that people tend to lock down. Whether that's
00:08:49.899 --> 00:08:52.379
because, you know, seen this, been there, done
00:08:52.379 --> 00:08:55.799
that. You know, it's too rote. It happens too
00:08:55.799 --> 00:08:59.039
often. Nothing surprises me. Nothing is like
00:08:59.039 --> 00:09:02.139
fun. I don't really get anything back from it
00:09:02.139 --> 00:09:03.960
except for, you know, a list of action items.
00:09:04.159 --> 00:09:06.220
So sort of giving people something to look
00:09:06.220 --> 00:09:09.340
forward to in that way. The honesty aspect comes
00:09:09.340 --> 00:09:12.919
from the creation of psychological safety and
00:09:12.919 --> 00:09:16.419
the disarmament through silliness. So once you
00:09:16.419 --> 00:09:18.259
have a team that's decided, we're actually going
00:09:18.259 --> 00:09:21.299
to do this, how do you go from, I want a more
00:09:21.299 --> 00:09:24.059
interesting retro to building out an entire fantasy
00:09:24.059 --> 00:09:27.080
world around it? Like, how do we even get started?
00:09:27.460 --> 00:09:30.240
Yeah, yeah. Great, great question. Talking about
00:09:30.240 --> 00:09:32.879
it can be very nebulous because I say, you know,
00:09:32.919 --> 00:09:35.289
like, it's different from a retro, but you can
00:09:35.289 --> 00:09:38.149
use the retro, but it's so much more, but you
00:09:38.149 --> 00:09:41.210
know, it can be very, um, also it doesn't happen
00:09:41.210 --> 00:09:43.549
in any other teams, except for the teams that
00:09:43.549 --> 00:09:46.210
I have been in. First of all, for our team, when
00:09:46.210 --> 00:09:48.509
I ran it, the team didn't really give me permission,
00:09:48.690 --> 00:09:51.129
but our manager did. And even our manager did
00:09:51.129 --> 00:09:54.389
not know what I was getting into. So he kind
00:09:54.389 --> 00:09:57.730
of just like, let me do it. He was sort of like,
00:09:57.830 --> 00:10:00.970
is it going to take, you know, the entire quarter?
00:10:01.070 --> 00:10:03.559
And the answer is no. Can you still do your other
00:10:03.559 --> 00:10:07.440
stuff? And yes. And does it push the team forward
00:10:07.440 --> 00:10:11.759
in terms of how we collaborate or in terms of
00:10:11.759 --> 00:10:14.460
how we understand our own strengths and weaknesses?
00:10:14.559 --> 00:10:17.019
Helps my manager sort of get a sense of like,
00:10:17.139 --> 00:10:19.440
where should I allocate particular resources?
00:10:19.899 --> 00:10:22.600
Where in my team are particular things kind of
00:10:22.600 --> 00:10:25.759
lacking? And it allows people, when we have those
00:10:25.759 --> 00:10:28.100
honest conversations, we can actually do something
00:10:28.100 --> 00:10:30.600
about the real problems. So the way that you
00:10:30.600 --> 00:10:32.919
start it is you ask your manager and you don't
00:10:32.919 --> 00:10:35.120
tell anyone else because it's super fun and silly
00:10:35.120 --> 00:10:37.659
when people have no idea what's coming. So the
00:10:37.659 --> 00:10:42.080
structure of Tabletop Retro is defined basically
00:10:42.080 --> 00:10:44.200
through a series of chapters that you take your
00:10:44.200 --> 00:10:47.860
team on. So a chapter is a container that's going
00:10:47.860 --> 00:10:51.179
to hold a portion of the story and at least one
00:10:51.179 --> 00:10:54.720
activity where the activity is, you know, it
00:10:54.720 --> 00:10:56.559
could be a typical retro activity, what went
00:10:56.559 --> 00:10:59.480
well and what we want to change. It can be a
00:10:59.480 --> 00:11:02.279
modified version. So you're like, you know, on
00:11:02.279 --> 00:11:04.980
my team, we run retros this way. Help ease your
00:11:04.980 --> 00:11:07.039
team into this experience by giving them something
00:11:07.039 --> 00:11:08.659
that they're a little bit familiar with. It can
00:11:08.659 --> 00:11:12.240
be straight up a game. So I've done some things
00:11:12.240 --> 00:11:15.299
in the past. There's always the option to put
00:11:15.299 --> 00:11:17.419
literal games in there. And that's part of silliness.
00:11:17.519 --> 00:11:19.559
That's part of disarmament. Also icebreakers.
00:11:20.220 --> 00:11:22.639
Icebreakers I use as a very, very generic term.
00:11:23.240 --> 00:11:26.179
So yeah, to be more concrete, there's chapters.
00:11:26.379 --> 00:11:30.029
Chapters hold stories and activities. And I find
00:11:30.029 --> 00:11:32.470
it easiest where I map one activity to one chapter
00:11:32.470 --> 00:11:36.240
and then we move on. Within these chapters, you
00:11:36.240 --> 00:11:40.700
are giving your team narrative, visual, potentially
00:11:40.700 --> 00:11:44.360
audio elements. So you kind of turn through pages
00:11:44.360 --> 00:11:46.600
and you show them pictures and you read them
00:11:46.600 --> 00:11:50.980
a story. And at the particular like plot point
00:11:50.980 --> 00:11:54.220
where you care about the mapping of what the
00:11:54.220 --> 00:11:57.059
narrative element is to what the team actually
00:11:57.059 --> 00:11:59.610
experienced. You hit them with an activity. Sometimes
00:11:59.610 --> 00:12:03.470
the activities are maybe outside of the context
00:12:03.470 --> 00:12:05.870
of the retro. They could be pretty dry. But because
00:12:05.870 --> 00:12:09.389
people are honed in to how weird this is, they
00:12:09.389 --> 00:12:12.169
actually kind of ignore it. So that's the structure.
00:12:12.409 --> 00:12:15.850
And so you would start with deciding, am I the
00:12:15.850 --> 00:12:19.070
person leading this retro? You are as the world
00:12:19.070 --> 00:12:22.169
builder and the experience curator and you go
00:12:22.169 --> 00:12:25.490
past or you go through the past, whatever, call
00:12:25.490 --> 00:12:27.669
it sprint. I do it annually. So we kind of look
00:12:27.669 --> 00:12:31.049
past in the past year. You create the world.
00:12:31.129 --> 00:12:34.450
You build a story. You take that story. You slice
00:12:34.450 --> 00:12:38.190
it up into chapters. You think about plot lines
00:12:38.190 --> 00:12:41.210
that map real experiences to the things that
00:12:41.210 --> 00:12:43.269
are happening to your characters. And you make
00:12:43.269 --> 00:12:45.690
people do activities. You take the input from
00:12:45.690 --> 00:12:48.269
those activities. You store them so that you
00:12:48.269 --> 00:12:51.230
can synthesize them and you can take the lessons
00:12:51.230 --> 00:12:54.769
from those later. So, you know, don't just remove
00:12:54.769 --> 00:12:58.730
all of the actual learning as the person running
00:12:58.730 --> 00:13:00.950
the retro. You get to synthesize those results
00:13:00.950 --> 00:13:04.549
later. And that's the kind of the structure of
00:13:04.549 --> 00:13:06.669
it. It's super loose because you get to do whatever
00:13:06.669 --> 00:13:10.590
you want. And so when you have people that are
00:13:10.590 --> 00:13:13.169
attending this retro, they've built these archetypes
00:13:13.169 --> 00:13:16.549
for this tabletop, how much of their character
00:13:16.549 --> 00:13:19.129
backstory was like just fun and how much like
00:13:19.129 --> 00:13:22.090
helped you actually build the actual retro? Yeah,
00:13:22.110 --> 00:13:26.009
so characters, as the person leading the retro,
00:13:26.090 --> 00:13:29.649
as the table lead, you can decide if your players
00:13:29.649 --> 00:13:31.830
are going to be characters or if they're going
00:13:31.830 --> 00:13:35.470
to be kind of their own people. Okay. So I've
00:13:35.470 --> 00:13:37.629
done it before where we're all, it's the same
00:13:37.629 --> 00:13:40.509
team. We're not, you know, in a fantasy world
00:13:40.509 --> 00:13:42.970
or anything, but we are all just kids doing trick-
00:13:42.970 --> 00:13:45.899
or-treating. There's not a lot that I'm like,
00:13:45.919 --> 00:13:49.879
add some fantasy elements here. The point of
00:13:49.879 --> 00:13:52.620
the technical archetype is somewhat twofold.
00:13:52.779 --> 00:13:56.139
So I set it up where you give me a character
00:13:56.139 --> 00:13:59.460
sheet, essentially, and the in-universe races
00:13:59.460 --> 00:14:03.899
that your character is are mapped to these technical
00:14:03.899 --> 00:14:06.740
archetypes. So we have, I forget what they are,
00:14:06.820 --> 00:14:09.399
but they're like, the Goliath is sort of like
00:14:09.399 --> 00:14:12.159
a high-level systems thinker. The Gnome is kind
00:14:12.159 --> 00:14:14.639
of like a... tinkering, automation engineer,
00:14:14.940 --> 00:14:17.759
things like that. So the first part about that
00:14:17.759 --> 00:14:22.419
is engagement in self-insertion. So you get
00:14:22.419 --> 00:14:27.039
to put pieces of yourself into this story and
00:14:27.039 --> 00:14:29.580
people get super stoked about that. It's almost
00:14:29.580 --> 00:14:33.519
like a horoscope where you say like, well, if
00:14:33.519 --> 00:14:36.679
you're a Gemini, it means this and that. And
00:14:36.679 --> 00:14:39.200
people love that. So I always give people the
00:14:39.200 --> 00:14:40.500
option where it's like, if you really want to
00:14:40.500 --> 00:14:42.679
be a gnome, but you don't care about automation,
00:14:42.940 --> 00:14:45.879
like that's fine, go be a gnome. But the second
00:14:45.879 --> 00:14:49.320
thing that that gives you in the character archetypes
00:14:49.320 --> 00:14:51.720
and the way that we did it is we talked about
00:14:51.720 --> 00:14:54.399
it as a team afterwards. So it's not like the
00:14:54.399 --> 00:14:57.960
secret mapping and, you know, I know what it
00:14:57.960 --> 00:14:59.700
means and you're telling me all these things
00:14:59.700 --> 00:15:01.679
about how you like to work. And then I hold that
00:15:01.679 --> 00:15:05.139
information for myself. As a team, we took time
00:15:05.139 --> 00:15:08.190
to introspect on the ways that we view ourselves,
00:15:08.509 --> 00:15:11.269
our strengths and weaknesses. And I find that
00:15:11.269 --> 00:15:14.330
to be so valuable. That's something that I try
00:15:14.330 --> 00:15:16.450
to do in every retro is to give people the ability
00:15:16.450 --> 00:15:19.809
to say like, I built this thing and this is kind
00:15:19.809 --> 00:15:22.250
of how I see myself. And this is how I see myself
00:15:22.250 --> 00:15:24.889
in the context of our team. It just, it helps
00:15:24.889 --> 00:15:26.710
everybody understand each other so much better
00:15:26.710 --> 00:15:29.629
and it leads to a better working experience and
00:15:29.629 --> 00:15:32.519
team cohesion. So that's characters. Yeah, it
00:15:32.519 --> 00:15:35.460
can be, again, as involved or not involved as
00:15:35.460 --> 00:15:38.629
you'd like. Did people's submissions change what
00:15:38.629 --> 00:15:41.610
you wrote and how you thought about their characters
00:15:41.610 --> 00:15:46.090
and the story? They didn't change how I felt
00:15:46.090 --> 00:15:49.350
about my co-workers as people, right? Something
00:15:49.350 --> 00:15:51.909
that I did, though, something that I would recommend,
00:15:51.970 --> 00:15:54.570
similar to how, you know, as a lead, you kind
00:15:54.570 --> 00:15:56.429
of have to delegate. As a senior engineer, you
00:15:56.429 --> 00:15:58.629
have to delegate. When you're a table lead in
00:15:58.629 --> 00:16:01.850
the Tabletop Retro as a game, you have to pick
00:16:01.850 --> 00:16:05.440
and choose, find this balance between, you know,
00:16:05.440 --> 00:16:08.580
I have to build this whole story. I have 24 hours
00:16:08.580 --> 00:16:10.820
in the day like everybody else. I want to give
00:16:10.820 --> 00:16:13.019
people the option to self-insert where they
00:16:13.019 --> 00:16:16.320
can. So when I asked for character sheets, I
00:16:16.320 --> 00:16:18.340
also said, you have to give me your backstory.
00:16:19.080 --> 00:16:22.299
So I had us, the campaign started where we were
00:16:22.299 --> 00:16:24.779
all imprisoned in the Hall of the Mountain King.
00:16:24.899 --> 00:16:26.340
And I didn't want to have to get these character
00:16:26.340 --> 00:16:28.820
sheets back and then say, you know, here's how
00:16:28.820 --> 00:16:31.399
all my friends got imprisoned. I forced everybody
00:16:31.399 --> 00:16:35.230
to... build a part of the world with me. So in
00:16:35.230 --> 00:16:37.210
that way, yeah, it actually gave me a lot of
00:16:37.210 --> 00:16:40.090
direction because people took that option for
00:16:40.090 --> 00:16:41.850
creativity and they sort of ran with it, right?
00:16:42.330 --> 00:16:46.830
Nobody said I was in prison because I stole a
00:16:46.830 --> 00:16:49.450
coin purse from an old lady and they locked me
00:16:49.450 --> 00:16:51.570
up, right? Everybody used it as an opportunity
00:16:51.570 --> 00:16:54.690
to dive more into their characters. And also,
00:16:54.750 --> 00:16:57.610
interestingly, everybody gave me a little breadcrumbs
00:16:57.610 --> 00:17:00.429
about the world that I was building. So I was
00:17:00.429 --> 00:17:03.840
able to use these crowdsourced ideas to build
00:17:03.840 --> 00:17:06.619
out the world in a much fuller way. Okay, so
00:17:06.619 --> 00:17:10.380
speaking of you have 24 hours in a day and you're
00:17:10.380 --> 00:17:12.920
building out this world, how much prep time did
00:17:12.920 --> 00:17:15.440
the whole thing take and what part took the longest?
00:17:15.900 --> 00:17:19.180
Yeah, interesting. I would say before I actually
00:17:19.180 --> 00:17:22.059
built out my own framework for it, which I can
00:17:22.059 --> 00:17:25.140
make available whenever we drop this, it took
00:17:25.140 --> 00:17:28.339
me a long time to figure out the right interfaces.
00:17:29.180 --> 00:17:31.059
So as we're talking about this, you know, I've
00:17:31.059 --> 00:17:32.880
talked about here's how you build the story.
00:17:33.000 --> 00:17:35.059
I mentioned, you know, you kind of show it like
00:17:35.059 --> 00:17:38.619
a book to your team. Speaking like specifically,
00:17:38.839 --> 00:17:43.779
it's any software that has like you can insert
00:17:43.779 -->
00:17:47.079
visual elements into it and you can constrain
00:17:47.079 --> 00:17:49.779
the audience view at any given time and potentially
00:17:49.779 --> 00:17:53.740
insert some audio elements as well. So like I've
00:17:53.740 --> 00:17:56.259
used Lucidchart, for example, like we will hop
00:17:56.259 --> 00:17:59.390
on a Zoom screen. I go through frames in Lucidchart,
00:17:59.450 --> 00:18:02.069
which just take you from one part of the diagram
00:18:02.069 --> 00:18:05.230
to another. And that was the way that I presented
00:18:05.230 --> 00:18:09.400
the pages in the book. For our team, when we
00:18:09.400 --> 00:18:11.819
did it last year, I used Canva and same sort
00:18:11.819 --> 00:18:13.940
of thing. It's basically a slideshow, right,
00:18:14.019 --> 00:18:16.680
where I have music and I have sounds. I have
00:18:16.680 --> 00:18:19.359
some images that are, you know, AI generated.
00:18:19.500 --> 00:18:22.220
I draw some things because just you don't have
00:18:22.220 --> 00:18:24.460
to draw things, but I like to draw things. So
00:18:24.460 --> 00:18:26.359
I make everybody look at my little drawings.
00:18:26.970 --> 00:18:30.349
And it's primarily the communication mechanism,
00:18:30.569 --> 00:18:32.809
right? So jump on a Zoom or a Slack huddle or
00:18:32.809 --> 00:18:37.109
something. Have a way for people to interact
00:18:37.109 --> 00:18:39.970
with your activities. That could just be a Slack
00:18:39.970 --> 00:18:41.769
channel. It could be Lucidchart. It could be
00:18:41.769 --> 00:18:44.470
whatever you use to run retros right now, as
00:18:44.470 --> 00:18:46.230
long as you can customize kind of the prompt
00:18:46.230 --> 00:18:51.250
and the options and stuff. So you can use whatever
00:18:51.250 --> 00:18:53.069
you want. And that's always going to take the
00:18:53.069 --> 00:18:55.210
biggest amount of time. If you'd like to cut
00:18:55.210 --> 00:18:57.420
through it. I'd recommend just using my framework
00:18:57.420 --> 00:19:00.019
that I built and it helps the table lead create
00:19:00.019 --> 00:19:03.019
these chapters, show them to your team. But you
00:19:03.019 --> 00:19:05.039
can truly use whatever you want as long as you
00:19:05.039 --> 00:19:08.500
can get the audio and as long as you can build
00:19:08.500 --> 00:19:11.279
a world for people. Very cool. So one of the
00:19:11.279 --> 00:19:13.099
things that I really liked about this idea is
00:19:13.099 --> 00:19:16.539
that the engineering discussion itself isn't
00:19:16.539 --> 00:19:19.519
separate from the game. It actually becomes like
00:19:19.519 --> 00:19:21.579
part of the game. How did you figure out how
00:19:21.579 --> 00:19:24.579
to do that? That's a great question. How do you
00:19:24.579 --> 00:19:27.099
do that? I think there's two things that have
00:19:27.099 --> 00:19:29.559
helped me, maybe three. Our team is just kind
00:19:29.559 --> 00:19:33.400
of silly. Like we are always, we naturally strike
00:19:33.400
--> 00:19:36.380
a really good balance between, you know, we are
00:19:36.380 --> 00:19:38.660
actively in a fire, but we're still kind of throwing
00:19:38.660 --> 00:19:40.359
jokes on the side, right? Like we're still kind
00:19:40.359 --> 00:19:42.759
of having a good time while we are still fixing
00:19:42.759 --> 00:19:45.079
things. Like we have that sort of natural ability.
00:19:45.299 --> 00:19:48.420
And in a lot of ways, the jokes help us de-stress,
00:19:48.440 --> 00:19:51.259
right? They make us better troubleshooters. So
00:19:51.259 --> 00:19:55.500
there's that for us. The second thing is oftentimes,
00:19:55.519 --> 00:19:57.819
I think when we describe something technical,
00:19:58.019 --> 00:20:00.859
especially if we are speaking to non-technical
00:20:00.859 --> 00:20:05.299
stakeholders, we will use metaphors. And as I
00:20:05.299 --> 00:20:09.660
tried to get better at communicating technical
00:20:09.660 --> 00:20:12.779
things to people who cannot speak that same language,
00:20:12.980 --> 00:20:16.319
the goal is to find that shared language, right?
00:20:16.460 --> 00:20:19.440
And metaphors can be really good. You can...
00:20:19.740 --> 00:20:22.180
use metaphors that are still kind of business
00:20:22.180 --> 00:20:24.180
related so that people who are more business
00:20:24.180 --> 00:20:25.980
minded have a good sense of what you're talking
00:20:25.980 --> 00:20:29.220
about. So when you deal with people who, you
00:20:29.220 --> 00:20:32.359
know, we all play video games, we love our escapism,
00:20:32.380 --> 00:20:35.579
we have some, you know, shared media that we
00:20:35.579 --> 00:20:39.460
like to dive into. It's an exercise in building
00:20:39.460 --> 00:20:42.740
a shared language and mapping things correctly,
00:20:43.000 --> 00:20:45.400
which is also, I think, just like a fundamental
00:20:45.400 --> 00:20:48.819
engineering skill. And having I would say also
00:20:48.819 --> 00:20:51.819
being somebody who gets excited about world building
00:20:51.819 --> 00:20:55.859
as well. If you don't like the idea that, you
00:20:55.859 --> 00:20:58.299
know, plot lines are going to have to require
00:20:58.299 --> 00:21:01.740
me to think about the political nature of how
00:21:01.740 --> 00:21:04.140
my characters and universe kind of interact with
00:21:04.140 --> 00:21:07.059
each other. In our land, in Terramont, land of
00:21:07.059 --> 00:21:09.509
mountains, you know, there are... There's like
00:21:09.509 --> 00:21:12.609
high court politics. There are things going on
00:21:12.609 --> 00:21:15.609
in the universe that I just personally care about
00:21:15.609 --> 00:21:18.170
because the world building is super, super fun.
00:21:18.509 --> 00:21:20.529
And if you don't like that, you're going to have
00:21:20.529 --> 00:21:22.509
a hard time finding these mappings. But I don't
00:21:22.509 --> 00:21:23.809
think it's impossible. I think you just have
00:21:23.809 --> 00:21:26.170
to make sure that the world you build isn't too
00:21:26.170 --> 00:21:28.910
complex. The world we've built is pretty complex.
00:21:29.089 --> 00:21:31.130
So I'm going to try to scope it down. Again,
00:21:31.269 --> 00:21:33.869
your kids playing trick-or-treating, going
00:21:33.869 --> 00:21:36.849
through a neighborhood, right? The world is smaller.
00:21:36.990 --> 00:21:39.650
The scope of your problems are smaller. The things
00:21:39.650 --> 00:21:41.170
that you'd have to care about or think about
00:21:41.170 --> 00:21:43.670
as far as mapping are also much more simple.
00:21:44.069 --> 00:21:46.589
Okay. So I kind of talked about this a little
00:21:46.589 --> 00:21:49.009
bit earlier, but I want to hone in on a little
00:21:49.009 --> 00:21:51.390
bit more. Do you think that people will say something
00:21:51.390 --> 00:21:54.210
through a character that they might hesitate
00:21:54.210 --> 00:21:56.710
to say in front of a normal retro board? Like,
00:21:56.710 --> 00:21:59.349
have you noticed this having done these? Yeah,
00:21:59.369 --> 00:22:01.890
I think it can be a double-edged sword, right?
00:22:02.009 --> 00:22:03.730
Like, especially once you introduce characters.
00:22:04.420 --> 00:22:07.079
Some people will feel very emboldened by that,
00:22:07.119 --> 00:22:09.859
right? And they'll say, you know, I'm an orc
00:22:09.859 --> 00:22:13.500
and I don't have a filter. And when I see something
00:22:13.500 --> 00:22:15.660
wrong going in Terramont, I'm going to say something
00:22:15.660 --> 00:22:18.019
about it. And maybe that's not even necessarily
00:22:18.019 --> 00:22:20.359
their typical communication style, right? And
00:22:20.359 --> 00:22:23.440
this character gives them the permission to say
00:22:23.440 --> 00:22:25.039
something that they would normally never say
00:22:25.039 --> 00:22:27.160
because it's in the game. You know, it's in the
00:22:27.160 --> 00:22:28.880
universe. It's not really how I feel. I'm just
00:22:28.880 --> 00:22:32.039
an orc. And some people will see role-playing
00:22:32.039 --> 00:22:33.900
or however you want to call it. As something
00:22:33.900 --> 00:22:37.000
that's kind of intimidating, you know, it takes
00:22:37.000 --> 00:22:38.940
them out of their comfort zone already. Maybe
00:22:38.940 --> 00:22:40.519
they're already comfortable talking in the team.
00:22:40.619 --> 00:22:46.200
What I like to do is give people options. So
00:22:46.200 --> 00:22:49.400
I do assign speaking lines in Tabletop Retro
00:22:49.400 --> 00:22:52.019
because I need to push the narrative forward.
00:22:52.240 --> 00:22:55.200
And part of moving the narrative forward is finding
00:22:55.200 --> 00:22:57.359
out how characters interact with each other,
00:22:57.460 --> 00:23:00.259
how they feel about the world, how they handle
00:23:00.259 --> 00:23:03.900
different NPCs, right? I gave my character speaking
00:23:03.900 --> 00:23:07.079
lines. I mean, you do have to be very tuned into
00:23:07.079 -->
00:23:10.019
your team. One of the character lines that I
00:23:10.019 --> 00:23:13.039
gave the past time when we ran it on our team,
00:23:13.119 --> 00:23:16.279
it was like an improv opportunity, but I gave
00:23:16.279 --> 00:23:19.960
it to, you know, he's my friend. Like he's very
00:23:19.960 --> 00:23:23.000
well known in the team. Like he's not a shy person.
00:23:23.299 --> 00:23:26.339
So I made him do an improv about like, we're
00:23:26.339 --> 00:23:28.240
trying to sneak past a guard. And I was like,
00:23:28.279 --> 00:23:31.240
but. He figured out like the exact thing to tell
00:23:31.240 --> 00:23:34.220
the guard, so he would let us through and then
00:23:34.220 --> 00:23:36.099
he failed. The persuasion didn't work. You know
00:23:36.099 --> 00:23:39.200
what I mean? Versus for other people on our team
00:23:39.200 --> 00:23:42.599
that I still wanted to use as pieces to move
00:23:42.599 --> 00:23:45.559
the plot forward, I would give them lines. So
00:23:45.559 --> 00:23:47.240
I would say like, all you have to do is say what's
00:23:47.240 --> 00:23:50.599
on the screen right now. And if you know your
00:23:50.599 --> 00:23:53.660
team, you know which one to pick for particular
00:23:53.660 --> 00:23:56.460
people or if they should just not have any speaking
00:23:56.460 --> 00:23:59.400
lines at all. The thing I would say that is a
00:23:59.400 --> 00:24:03.519
little bit less negotiable for me is tabletop
00:24:03.519 --> 00:24:08.079
retro I use as an opportunity for people to showcase
00:24:08.079 --> 00:24:10.599
things, almost like mini knowledge sharing sessions.
00:24:10.900 --> 00:24:14.759
And that I do expect people to, you don't have
00:24:14.759 --> 00:24:18.660
to participate in character, but that I am very
00:24:18.660 --> 00:24:20.839
particular about, you know, we're just going
00:24:20.839 --> 00:24:24.490
to talk about the... Our new cluster architecture,
00:24:24.849 --> 00:24:26.509
you're the best person to talk to us about it.
00:24:26.589 --> 00:24:28.309
Like, let's not do metaphors. We're not going
00:24:28.309 --> 00:24:30.829
to do mappings. We're just going to hone in and
00:24:30.829 --> 00:24:33.089
we'll map it to something silly after the fact.
00:24:33.250 --> 00:24:36.730
So there's certainly a balance and you have to
00:24:36.730 --> 00:24:39.670
be attuned to your team. So I wouldn't say, you
00:24:39.670 --> 00:24:42.289
know, get a new job, come in, first retro you
00:24:42.289 --> 00:24:45.910
ever do is Tabletop Retro. Get a sense of where
00:24:45.910 --> 00:24:48.950
your team's at. You know, what are the issues
00:24:48.950 --> 00:24:52.109
that require... a whole world to be built around
00:24:52.109 --> 00:24:54.690
them. Everything that you're doing here should
00:24:54.690 --> 00:24:58.509
be intentional. Every time you're silly, every
00:24:58.509 --> 00:25:01.029
time you put in a game, it should be for a purpose.
00:25:01.450 --> 00:25:06.029
And at the end of it all, you
should have a sense
00:25:06.029 --> 00:25:08.930
of if you've met your desired outcomes for that
00:25:08.930 --> 00:25:11.809
retro. And just like any other retro, if you
00:25:11.809 --> 00:25:14.869
feel like people weren't honest, no one knows
00:25:14.869 --> 00:25:18.009
what to do. We're all still unaligned and nobody
00:25:18.009 --> 00:25:20.970
even knows what the actual failure points of
00:25:20.970 --> 00:25:23.990
this team are, the Tabletop Retro won't help
00:25:23.990 --> 00:25:27.069
you, right? A regular retro and Tabletop Retro
00:25:27.069 --> 00:25:29.410
will fail in that same way. So is that how you'd
00:25:29.410 --> 00:25:32.869
consider a failure of a Tabletop Retro is that
00:25:32.869 --> 00:25:35.890
you don't have those outcomes? Just like you
00:25:35.890 --> 00:25:37.490
wouldn't for a normal retro, I guess. So is it
00:25:37.490 --> 00:25:40.910
the same bar for normal retro versus the tabletop?
00:25:40.910 --> 00:25:43.230
Or do you look at those differently? I would
00:25:43.230 --> 00:25:45.609
look at them as the same. And actually, I would
00:25:45.609 --> 00:25:49.000
even raise the bar for Tabletop Retro sort of
00:25:49.000 --> 00:25:52.119
assertion is that when you put a little bit more
00:25:52.119 --> 00:25:54.779
of yourself into this, we're all going to put
00:25:54.779 --> 00:25:56.740
a little bit more of ourselves into this. And
00:25:56.740 --> 00:26:00.200
it's going to give us an insight that we previously
00:26:00.200 --> 00:26:03.339
could not get. For regular retro, I feel like
00:26:03.339 --> 00:26:05.619
sometimes the bar is like, we've talked about
00:26:05.619 --> 00:26:09.140
the past two weeks, you know? So yeah, the ways
00:26:09.140 --> 00:26:11.579
to fail are very similar, but the bar is higher
00:26:11.579 --> 00:26:15.539
for Tabletop Retro because you bring in this
00:26:15.539 --> 00:26:19.589
nuanced super weapon. And so you expect the results
00:26:19.589 --> 00:26:22.609
to be something where I can be almost pinpointed
00:26:22.609 --> 00:26:26.269
or I can gain something out of this experience
00:26:26.269 --> 00:26:30.150
that previously was locked away from me. So a
00:26:30.150 --> 00:26:33.210
failed Tabletop Retro is nobody had fun. Nobody
00:26:33.210 --> 00:26:36.930
laughed even once. We wasted a bunch of time
00:26:36.930 --> 00:26:40.250
and we never want to do it again. Yeah, that's
00:26:40.250 --> 00:26:42.829
fair. Okay. So my question is, if I'm listening
00:26:42.829 --> 00:26:45.410
to this podcast, I'm hearing, okay, this sounds
00:26:45.410 --> 00:26:47.849
really interesting. I want to do this. Maybe
00:26:47.849 --> 00:26:50.089
a Halloween theme, maybe a Christmas theme, whatever,
00:26:50.289 --> 00:26:54.210
like some yearly cadence. How do I start? I hear
00:26:54.210 --> 00:26:56.970
this episode, I get your resources. What's the
00:26:56.970 --> 00:26:58.950
minimum viable? And we kind of talked about that
00:26:58.950 --> 00:27:01.230
a little bit with the trick-or-treating, but
00:27:01.230 --> 00:27:04.950
is there just a quick outline of how do I start?
00:27:05.089 --> 00:27:09.450
Is it D&D-based? Do I need to have dice? Do
00:27:09.450 --> 00:27:13.390
I have everyone pick their archetypes? How do
00:27:13.390 --> 00:27:16.029
I even start without just taking on too much?
00:27:16.349 --> 00:27:20.079
Yeah, for sure. So the very first thing, and
00:27:20.079 --> 00:27:23.019
this is similar to, you know, how do I start
00:27:23.019 --> 00:27:26.119
building a software product? You could just like
00:27:26.119 --> 00:27:28.420
begin, right? And you're like, I don't know.
00:27:28.579 --> 00:27:31.319
Let's just start having robots generate code
00:27:31.319 --> 00:27:33.319
and we're going to do something with it. Like
00:27:33.319 --> 00:27:37.140
I was talking about kind of with the idea that
00:27:37.140 --> 00:27:39.180
it should produce something, you should figure
00:27:39.180 --> 00:27:42.440
out what it should produce, right? You need to
00:27:42.440 --> 00:27:45.960
be involved enough in your team. Talk to the
00:27:45.960 --> 00:27:47.680
people on your team, talk to your manager, figure
00:27:47.680 --> 00:27:50.819
out pieces that your manager is still having
00:27:50.819 --> 00:27:53.220
issues with, right? We're not clicking in this
00:27:53.220 --> 00:27:55.900
one particular way. You have to find those problems
00:27:55.900 --> 00:27:59.500
and then you have to, what's the right word?
00:27:59.599 --> 00:28:01.460
You have to distill the right questions from
00:28:01.460 --> 00:28:04.039
those problems. I think the right question is
00:28:04.039 --> 00:28:06.079
not going to be like, oh, how do we fix this?
00:28:06.299 --> 00:28:09.940
Right? The right question is more in what specific
00:28:09.940 --> 00:28:13.660
ways are we unaligned? When specifically? Is
00:28:13.660 --> 00:28:16.980
our communication breaking down? What are the
00:28:16.980 --> 00:28:20.359
stories that my team individually, they're telling
00:28:20.359 --> 00:28:24.359
themselves? And how are those stories different
00:28:24.359 --> 00:28:27.019
from how I would prefer us to operate as a team?
00:28:27.140 --> 00:28:30.380
Or which of their stories are actually unaligned
00:28:30.380 --> 00:28:33.460
from the entire team story? Do we understand
00:28:33.460 --> 00:28:38.039
our posture in specific things in how we do,
00:28:38.240 --> 00:28:41.430
you know, how's our security posture? When do
00:28:41.430 --> 00:28:43.589
we say yes to things versus when do we say no
00:28:43.589 --> 00:28:45.789
to things? What are the appropriate communication
00:28:45.789 --> 00:28:50.809
channels? Where are the secret hidden things
00:28:50.809 --> 00:28:54.490
that our engineers get beat down on time and
00:28:54.490 --> 00:28:56.250
time again, but they're not telling anybody about
00:28:56.250 --> 00:28:58.670
it? I think that's great. I would even argue
00:28:58.670 --> 00:29:01.150
that
that's important for even normal retros.
00:29:01.150 --> 00:29:03.930
I think a lot of people lose that guidance in
00:29:03.930 --> 00:29:06.029
what the outcomes of a retro should be. I think
00:29:06.029 --> 00:29:08.529
that's well said. Yeah, I actually really agree
00:29:08.529 --> 00:29:11.000
with that. And that's another kind of... hidden
00:29:11.000 --> 00:29:14.400
trap on doing something that's very rote on a
00:29:14.400 --> 00:29:18.900
cadence that leads to an almost monotony, right?
00:29:18.920 --> 00:29:20.660
As you forget, wait, why are we doing this? It's
00:29:20.660 --> 00:29:22.900
just something we do, right? Versus when it's
00:29:22.900 --> 00:29:27.279
this novel, bespoke experience, you have to justify
00:29:27.279 --> 00:29:30.599
it right up front. And it requires a lot of thought
00:29:30.599 --> 00:29:34.640
and intention and introspection before you bring
00:29:34.640 --> 00:29:37.240
in the whole team for introspection. So yeah,
00:29:37.319 --> 00:29:42.240
be in the team, figure out what your friction
00:29:42.240 --> 00:29:45.119
points are, what the problems you are, what you're
00:29:45.119 --> 00:29:47.220
seeing happen in your team. Make sure that you're
00:29:47.220 --> 00:29:49.079
asking the right questions about those problems.
00:29:49.579 --> 00:29:52.920
It's possible that some of those questions are
00:29:52.920 --> 00:29:55.339
the classic three, what could we be doing better?
00:29:55.819 --> 00:29:59.380
But it should seek to expand much more, right?
00:29:59.420 --> 00:30:02.180
Again, we have this machine that can create a
00:30:02.180 --> 00:30:04.980
lot of nuance. So add that nuance to your questions.
00:30:05.440 --> 00:30:08.720
Once you have your desired outcomes, just pick
00:30:08.720 --> 00:30:11.839
a setting. Pick a world, pick a time. Again,
00:30:11.940 --> 00:30:14.599
how much do you want to put yourself into this?
00:30:14.660 --> 00:30:16.420
How complex do you want it to be? Is there a
00:30:16.420 --> 00:30:18.200
thing on your team that everybody bonds over
00:30:18.200 --> 00:30:21.099
already? We're all big Star Wars nerds. Let's
00:30:21.099 --> 00:30:23.599
start there. Maybe not necessarily Star Wars
00:30:23.599 --> 00:30:26.640
TM, the universe, but we're all in space. We
00:30:26.640 --> 00:30:29.019
have laser swords or whatever it's going to be.
00:30:29.660 --> 00:30:33.420
Use my framework or any other pieces of technology
00:30:33.420 --> 00:30:36.700
to create essentially a storybook. You're going
00:30:36.700 --> 00:30:40.799
to move chapter by chapter. The questions that support your
00:30:40.799 --> 00:30:44.099
desired outcomes are eventually going to be mapped
00:30:44.099 --> 00:30:47.140
into specific plot lines alongside your activities
00:30:47.140 --> 00:30:49.880
within those chapters. Add some audio, figure
00:30:49.880 --> 00:30:52.200
out the twists and turns in the story. This is
00:30:52.200 --> 00:30:54.180
just regular storytelling, regular world building.
00:30:54.619 --> 00:30:58.140
Again, we had this idea that I'm going to help
00:30:58.140 --> 00:31:02.200
my players inject themselves by giving them characters,
00:31:02.559 --> 00:31:05.140
having those characters mapped to technical archetypes.
00:31:05.619 --> 00:31:09.480
That... sentiment is less about technical archetypes
00:31:09.480 --> 00:31:11.779
and more about, tell me something about yourself
00:31:11.779 --> 00:31:14.500
that maybe we've never asked directly before,
00:31:14.759 --> 00:31:16.819
right? Like, do you get asked when you come in,
00:31:16.880 --> 00:31:18.480
like, well, what kind of stuff do you like to
00:31:18.480 --> 00:31:21.400
do? Not typically, you know, it's usually go
00:31:21.400 --> 00:31:23.680
do the stuff that needs to be done, right? And
00:31:23.680 --> 00:31:25.880
that's certainly the case, right? You can tell
00:31:25.880 --> 00:31:28.279
me, you know, I don't ever want to look at IaC
00:31:28.279 --> 00:31:32.339
again and I will say, okay. Doesn't matter. Like
00:31:32.339 --> 00:31:34.839
we're going to move on. Right. But allowing people
00:31:34.839 --> 00:31:37.140
to tell you something about themselves that they've
00:31:37.140 --> 00:31:39.240
never been asked before or they've never felt
00:31:39.240 --> 00:31:42.339
like they needed to state before. Get everyone
00:31:42.339 --> 00:31:45.799
together at a time that they like. You can do
00:31:45.799 --> 00:31:49.200
it. You know, I tend to do Zoom, share my screen.
00:31:49.359 --> 00:31:53.680
I click through. I prompt people when to speak.
00:31:53.940 --> 00:31:56.640
We have the chat open. We have our activities
00:31:56.640 --> 00:32:00.150
that people type into. We'll do the reactions
00:32:00.150 --> 00:32:02.690
in Zoom, you know, when people get excited about
00:32:02.690 --> 00:32:04.950
something, almost like a standard meeting. Yeah,
00:32:04.950 --> 00:32:08.170
that's cool. Okay, so wrapping up, you've spent
00:32:08.170 --> 00:32:09.970
a lot of time thinking about retros, clearly.
00:32:10.529 --> 00:32:12.750
Do you have opinions on what you think engineering
00:32:12.750 --> 00:32:15.710
teams in general are getting wrong around retrospectives
00:32:15.710 --> 00:32:18.789
and what they could be doing better? Yeah, I
00:32:18.789 --> 00:32:23.069
mean, we've hit on it a lot as far as does it
00:32:23.069 --> 00:32:27.619
feel rote? Does it feel monotonous? Does it feel
00:32:27.619 --> 00:32:30.440
like an opportunity to shut my brain down instead
00:32:30.440 --> 00:32:32.819
of what it should be, which is an opportunity
00:32:32.819 --> 00:32:36.180
to engage? Does anything happen from it? This
00:32:36.180 --> 00:32:40.119
is a shared, I guess, potential problem between
00:32:40.119 --> 00:32:42.759
Tabletop Retro and any other retros. Is this
00:32:42.759 --> 00:32:46.440
just a space to complain about things and to
00:32:46.440 --> 00:32:49.339
receive additional work? Or is this an
opportunity
00:32:49.339 --> 00:32:55.539
for basically a contract to be made where I say,
00:32:56.099 --> 00:32:59.559
Give me more of yourselves. And in return, I'm
00:32:59.559 --> 00:33:03.500
going to find a way to actually do something
00:33:03.500 --> 00:33:07.160
about these things, right? So the retros typically
00:33:07.160 --> 00:33:09.779
kind of, in my opinion, they fall short from
00:33:09.779 --> 00:33:12.539
getting people to fully experience a story and
00:33:12.539 --> 00:33:15.500
to be fully honest. But the thing that could
00:33:15.500 --> 00:33:18.680
fail for both of them is that as a leader of
00:33:18.680 --> 00:33:22.720
your team, you don't seek to fix any of the problems.
00:33:22.900 --> 00:33:24.640
The worst thing, actually, maybe this is my answer.
00:33:25.140 --> 00:33:27.619
Another way that Tabletop Retro can be a failure
00:33:27.619 --> 00:33:30.779
is everyone has fun and it's amazing. And they
00:33:30.779 --> 00:33:33.759
think the story is great. And you ask all of the
00:33:33.759 --> 00:33:35.960
right questions, you do all the right plot lines.
00:33:36.539 --> 00:33:39.960
People tell you things that blow your mind with
00:33:39.960 --> 00:33:42.680
how honest and direct and succinct they are.
00:33:43.230 --> 00:33:46.309
And then you don't do anything with it. And then
00:33:46.309 --> 00:33:48.569
that's the end of it. I think that's a failure
00:33:48.569 --> 00:33:52.970
because all it does is just give us a fun little
00:33:52.970 --> 00:33:57.849
time. But what we need is to work better as an engineering team
00:33:57.849 --> 00:34:01.650
in the future. We need to do something that enables
00:34:01.650 --> 00:34:04.769
our, enables our engineers to be more effective.
00:34:04.769 --> 00:34:06.869
And that's actually, that's the thing I care about,
00:34:06.869 --> 00:34:09.469
right? Telling a fun story is secondary, or like,
00:34:09.469 --> 00:34:12.130
building a world for people is super fun and
00:34:12.130 --> 00:34:14.949
great, whatever. The thing I really want is for
00:34:14.949 --> 00:34:19.989
us to do a better job at our jobs and to be in
00:34:19.989 --> 00:34:22.769
a mentality, we're always thinking about that,
00:34:22.769 --> 00:34:25.210
we're always thinking like, how could this be
00:34:25.210 --> 00:34:28.650
done better? Or what failure modes have we sort
00:34:28.650 --> 00:34:30.570
of fallen into as a team time and time again
00:34:30.570 --> 00:34:32.610
that we can't get out of for whatever reason?
00:34:32.809 --> 00:34:35.150
Where can people find out more about you and
00:34:35.150 --> 00:34:39.349
talks, that sort of thing? Yeah, I don't know.
00:34:39.389 --> 00:34:41.050
I should have a website, huh? Maybe I'll have
00:34:41.050 --> 00:34:44.590
a website. Okay. You can just hit me up on LinkedIn.
00:34:44.849 --> 00:34:47.869
Yeah, that's the only thing I have. Yeah, go
00:34:47.869 --> 00:34:49.670
ahead. Connect with me on LinkedIn. I'll post
00:34:49.670 --> 00:34:53.980
stuff on there. We can talk about retros or engineering
00:34:53.980 --> 00:34:57.599
enablement. I also have a talk that I did recently
00:34:57.599 --> 00:35:00.739
for IaCConf about Terraform module interface
00:35:00.739 --> 00:35:03.420
design. It has nothing to do with anything we've
00:35:03.420 --> 00:35:04.860
talked about here. But if you're interested in
00:35:04.860 --> 00:35:07.619
that as well, that's available online. Cool.
00:35:07.639 --> 00:35:11.260
Very cool. I'll put links for the retro resources,
00:35:11.699 --> 00:35:14.820
your IaCConf talk, your LinkedIn, any other resources
00:35:14.820 --> 00:35:16.840
in the show notes. Jinger, thank you so much
00:35:16.840 --> 00:35:18.730
for joining me. Really appreciate it. Awesome.
00:35:18.750 --> 00:35:20.690
Thank you so much. I'm so stoked that I got to
00:35:20.690 --> 00:35:23.769
do this. That was my conversation with Jinger
00:35:23.769 --> 00:35:26.710
Meilani from Mountain. The biggest takeaway for
00:35:26.710 --> 00:35:30.429
me is that a Tabletop Retro is still a retro.
00:35:30.789 --> 00:35:35.070
Jinger calls it retro plus plus plus. All the
00:35:35.070 --> 00:35:38.809
normal retro stuff is still in there. The story
00:35:38.809 --> 00:35:42.510
is how she gets people to actually engage. Her
00:35:42.510 --> 00:35:45.530
smoothie line nailed it. Hide the vegetables
00:35:45.530 --> 00:35:49.340
in the fruit. And people give you honest answers,
00:35:49.559 --> 00:35:52.699
sometimes without realizing what you're asking.
00:35:52.960 --> 00:35:55.920
She won't run one during a fire. People have
00:35:55.920 --> 00:35:59.340
to feel safe to tell you the truth. So the flame-
00:35:59.340 --> 00:36:02.699
breathing dragon can wait. And characters cut
00:36:02.699 --> 00:36:06.019
both ways. For some people, playing an orc is
00:36:06.019 --> 00:36:09.420
permission to speak up. For others, role-play
00:36:09.420 --> 00:36:13.519
is the scary part. So she reads the room. Want
00:36:13.519 --> 00:36:16.800
to try one? Start with the questions, not the
00:36:16.800 --> 00:36:20.900
world. Where is the team out of sync? Where is
00:36:20.900 --> 00:36:24.719
communication breaking down? Then keep the setting
00:36:24.719 --> 00:36:28.880
small. Kids trick-or-treating is plenty. Honestly,
00:36:29.039 --> 00:36:32.940
that's good advice for a normal retro too. Last
00:36:32.940 --> 00:36:36.159
one. If everyone has a blast, tells you something
00:36:36.159 --> 00:36:39.860
honest, and nothing changes, you just had a fun
00:36:39.860 --> 00:36:43.300
afternoon. Someone still has to do the work.
00:36:43.539 --> 00:36:46.820
You can find Jinger on LinkedIn, plus a talk
00:36:46.820 --> 00:36:49.460
she gave on Terraform module interface design
00:36:49.460 --> 00:36:53.099
through the links in the show notes. Her tabletop
00:36:53.099 --> 00:36:57.460
retro framework is linked there too. Follow or
00:36:57.460 --> 00:37:00.260
subscribe to Ship It Weekly wherever you listen,
00:37:00.400 --> 00:37:04.099
and find previous episodes at shipitweekly.fm.
00:37:04.260 --> 00:37:06.780
Thanks for listening, and I'll see you later
00:37:06.780 --> 00:37:07.280
this week.