►
Description
Within this timezone group, various domain counterparts (Engineering Managers, Product Designers, Product Managers, Technical Writer, and/or UX Researcher) contribute to a User Journey Map (UJM) that spans the whole Create stage.
More information:
- Epic: https://gitlab.com/groups/gitlab-org/-/epics/6964
- Issue: https://gitlab.com/gitlab-org/create-stage/-/issues/12945
A
Recording
there
you
go
so
welcome
to
the
final
session,
the
wrap-up
session
for
the
create
user
journey
map,
and
this
is
the
americas
time
zone
group
one
and
let
me
share
my
screen
to
walk
you
through
what
we're
going
to
do
today.
A
A
I
consolidated
the
stickies
that
we
brainstormed
and
moved
them
down
to
the
map
section
to
the
steps
lane,
and
I
asked
you
to
asynchronously
contribute
to
the
other
lanes,
actions,
feelings,
pinpoints
and
opportunities,
and
today
what
we're
going
to
do
is
we're
going
to
go
through
all
of
these
stickies
and
basically
talk
about
them
and
rate
and
vote
on
our
confidence
levels
for
each
for,
for
the,
in
this
case,
try
to
vote
on
the
ones
that
have
the
least
confidence
on.
A
So
I
will,
you
know,
walk
you
through
the
whole
thing
and
tell
you
the
time
is
in
all
of
that,
but
what
we're
going
to
do
now
is
I'm
going
to
set
the
timer
for
five
minutes,
and
I
would
like
everyone
to
review
the
existing
user
journey
and
you
can
add
questions
and
thoughts
as
comments.
A
So
for
that
you
can
just
right.
Click.
A
sticky
and
click
add
comments.
If
you
have
any
comments
or
thoughts
about
it,
you
can
also
add
the
new
stickies
if
you
go
through
them
and
find
that
you
think
something
is
interesting
to
add.
But
ultimately,
what
I'd
like
to
focus
on
is
what
you
have
the
least
confidence
on,
and
this
is
to
help
with
that.
I
have
some
questions
here
so
which
ones
are
you
unsure
if
sasha
does
feels
things
or
experiences?
So
sasha
is
our
persona?
A
A
Sometimes
you
also
have
stickies
with
actions
and
feelings
and
pinpoints
that
are
more
gitlab
specific
and
that
affect
us
at
gitlab,
but
maybe
we're
not
sure
if
this
is
a
prevalent
issue
or
a
prevalent
action
that
most
organizations
do
or
most
engineers
at
other
organizations,
so
yeah
just
things
for
us
to
follow
up
on
and
dig
deeper
to
find
what
they're
all
about,
and
if
you
don't
find
a
specific
sticky
like,
for
example,
in
one
of
the
other
sessions.
A
There
was
a
big
doubt
around
the
this
beginning
part
the
define,
locate,
prepare
and
confirm,
or
even
in
another
group
they
didn't
have
anything
for.
I
think
the
monitor
part,
so
they
thought
okay.
So
we
think
we
need
to
understand
more
what
happens
in
the
monitor
part,
so
that's
something
that
they
had
least
confidence
on.
A
A
Yes,
everything
in
this
map
section,
so
steps
actions,
feelings,
pain,
points
and
opportunities.
Anything
goes.
A
Okay,
so
I'll
start
the
timer
and
have
fun
so
airplane
sounds
now.
C
D
Baby,
I
can
see
you
drinking
too
much
tipsy
because
you
sipping
on
your
gold,
dutch,
some
call
it
rough,
but
I
just
call
it
low
touch
compliment
you
as
a
toast
touch
in
a
reebok
heart
fermenting.
As
a
rolled
up
your
knee
sucks,
your
tear
drops
collect
on
the
tail
of
your
red
top
loaf.
So
deep
I'd
be
hitting
bedrock.
D
The
lead
stops
until
I
get
my
head
on
liquid
love
on
the
rocks
cup
of
tea,
with
some
scotch
describe
your
day
and
your
sucks
I'm
addicted
to
you,
a
victim
of
my
own
plot
depicts
a
life.
I
forgot
I'm
sick
of
right.
My
wrongs.
Illicit
love
is
enough
from
what
was
left
in
my
cup
symbolizes
when
to
give
up
somewhere.
When
that
is
a
lesson
you
can
pick
up,
I'm
sick
of
being
such
a
sucker
for
a
kiss,
your
lips,
atonic
and
gin.
The
saga
begins.
D
I
want
to
pretend
condemn
for
my
sins
flipping
predicaments
sniffing
in
cigarettes
kissing
through
a
silhouette.
You'll
soon
forget
the
moon
reflects
the
mind
you
used
to
know,
chimes
about
her
arm
and
with
the
rapid
growth
to
midnight
hope.
But
if
they
choke
cause,
she
sips
I
smoke
lips
are
provoked.
We
risk
our
moments
below
our
noses
tricking
the
roses
in
a
pocket
full
of
homes,
baby
drinking
too
much.
C
D
C
A
People
want
one
more
minute
to
review,
or
is
everyone
one
more
minute.
C
A
A
A
So
now
what
we're
going
to
do
is
we
have
some
some
comments
here
that
a
few
people
added
I
think
most
of
them
have
to
do
with
confidence
of
things
that
we
need
to
do
more
research,
unless
there
are
specific
questions
that
kai
and
eric
would
like
to
to
ask
now
and
are
more
related
to
clarity
of
the
stickies.
F
I
think
mine
was
confidence
if
that's
a
thing
that
the
person
does
necessarily
there
there's
a
it
feels
like
there's
a
lot
of
project
management
in
sasha's
life,
and
it's
not
clear
if,
if
that's
something
sasha
does
so
it's
like.
I
asked
a
bunch
I
sort
of
like
peppered
the
stickies
around
or
comments
on
some
of
those,
but
it
was
more
like
yeah
that
was
sort
of
my
thought.
C
G
My
my
comment
was
more
around
confidence
and
whether
or
not
this
is
limited
to
gitlab,
but
also,
I
think,
to
kai's
point.
If
we
look
back
up
at
the
persona,
it
says
30
to
40
percent
of
their
time.
Sasha's
time
is
taking
up
doing
non-engineering
task,
so
I
think
that's
probably
an
opportunity
to
clarify
in
this
user
journey
like
is
that
stuff
that
she
should
be
doing
or
is
necessary,
or
can
we
take
that
time
back
so
that
that
might
be
the
the
meta
discussion.
A
I
think
that's
a
very
interesting
point
about
potentially
highlighting
areas
that
are
more,
not
necessarily
shallow
work,
but
is
not
the
core
responsibility
of
this
persona.
A
You
know
like
managing
the
development
environment
to
make
sure
it
doesn't
break.
It's
not.
You
know
the
core
thing,
but
anyway
yeah.
I
think
all
of
those
are
good
questions,
but
I
think
those
are
more
related
to
the
confidence
levels
and
not
so
much
the
clarity
or
thoughts
about
what's
already
here.
A
So
what
we're
going
to
do
now
is
we're
going
to
I'm
going
to
ask
each
person
to
once
one
at
a
time,
five
minutes
each
to
share
the
seekies,
that
you
have
the
least
confidence
on
and
also
explain
why
so
it's
similar
to
what
you
were
just
doing
now
eric,
but
maybe
adding
a
bit
more
context
if
needed
and
also
other
people,
are
invited
to
participate
and
explain
what
they
think
as
well.
So
let
me
stop
the
timer
so
who
who
wants
to
go?
First,
I
think
kai.
A
Okay,
so
I'll
add
five
minutes
on
the
timer
and
I
will
follow
you,
and
so
we
can
see
exactly
what
you're
looking
at
you
don't
need
to
share
your
screen
and
yeah
just
share
the
the
top
first.
You
know
the
top
thing
that
you
don't
have
a
lot
of
confidence
on
and
we'll
go
from
there.
I
don't
feel
we
will
have
time
to
go
through
all
of
them.
F
F
F
And
even
like
locate
like,
I
wonder
if
every
time
they
do
this
job,
if
this
is
like
they
do
these
things
like
reading
documentation,
I
don't
know
I
guess
that
was
sort
of
my
other
pieces
like
it's
not
clear.
If
these
are
every
time
asks
so
yeah
I
have,
I
think,
the
project
management
ones
and
then
the
gdk
one.
There
was
a
lot.
That's
like
very
git
lab
specific,
but
also
I
hear
our
engineers
complain
about
it,
but
I
also
hear
the
people
who
don't
use
it
very
frequently
complain
more.
A
I
think
that
that's
valid,
and
it
would
also
be
interesting
for
us
to
highlight
that
in
the
journey
map
that
certain
things
don't
happen
all
the
time,
but
are
important
parts
that
we
want
to
record
and
see
and
visualize
here
like
reading
and
documentation
or
adding
labels.
Maybe
that
doesn't
happen
all
the
time,
but
it's
certainly
something
important
okay.
So,
let's,
let's
in
the
minutes
that
we
have
left,
let's
talk
a
little
bit
about
the
the
project
management
ones
that
you
highlighted.
A
G
I
I
guess
I
was
just
going
to
comment
that
I
don't
think
this
is
necessarily
just
a
gitlab
thing
right,
like
I
mean
I've
been
on
other
engineering
teams
and
they
all
had
to
work
in
jira
issues
or
some
other
project
management
to
communicate
status
and
pick
up
work
off
a
board
whether
it's
trello
or
jira.
G
G
C
F
F
A
Yeah
yeah,
yeah
and
interestingly
like
here
we're
all
create
folks,
but
this
user
journey
is
so
big
that
it
could
certainly
benefit
from
contributions
from
any
other
teams
like
plan
and
and
that's
the
great
thing,
that's
exactly.
The
whole
goal
of
this
exercise
is
try
to
break
these
walls
down.
We
couldn't
invite
everyone
in
all
stage
groups
that
contribute
to
this
experience.
A
Sasha's
experience
with
this
job
to
be
done,
but
certainly
something
that
we
can
highlight
and
also
ask
from
gabe's
team
if
they
have
more
input
on
this
and
help
improve
this
user
journey
all
right.
Okay,
so
thanks
kai
now
who
wants
to
go
next
and
share
the
the
top
or
a
few
of
the
top
things
that
they
have
the
least
confidence
on.
E
G
G
I'm
curious
whether
this
is
a
gdk
problem
or
if
it's
any
moderately
complex
development
environment
at
any
organization.
So
I
guess
that's
that's
the
the
question
and
maybe
the
opportunity
to
research
is
whether
or
not
or
I
should
say
how
often
organizations
have
challenges
like
we
have
with
the
gdk.
G
Yeah,
I
think,
that's
that's
probably
how
I'd
sum
it
up.
I
don't
I
mean
I
know
that
there
are
opportunities
out
there
to
simplify
development
environments
and
setting
up
development
environments,
and
things
like
that.
So
maybe
it's
just
a
chance
to
dig
in
to
those
areas
and
research
what
the
actual
benefits
are
to
individual
contributors
and
how
often
they
run
into
these
things.
If
they
are
the
ones
like
I
said
that
are
day-to-day
using
it,
maybe
maintaining
their
local
environments.
G
A
Yeah
yeah
for
sure
yeah
this
is
this
was
a
point
that
came
up
in
the
other
sessions
as
well.
People.
Of
course,
you
know
mentioned
gdk
directly,
but
overall
we
we
thought
that
this
was
a
generic
issue
that
could
affect
more
some
organizations
more
than
others,
depending
on
their
tooling
so
yeah.
We
could
abstract
this
to
a
pain
point
that
affects
all
kinds
of
organizations
with
their
development
environments
and
maybe
there's
an
opportunity
here
for
gitlab
to
do
something
or
not,
but
I
think
it's
important
that
we
acknowledge
that
in
the
user
journey.
A
Else,
mike
matt
yeah.
E
On
that
note,
I
think
kind
of
combining
what
kai
said
to
that
there's
different
levels
of
I
don't
know
if
we
say
battling
but
like
of
getting
your
development
environment
working
the
first
time
it
might
take
a
long
time
if
you're
constantly
doing
it.
E
You
probably
have
to
do
a
little
bit
every
time,
but
it
seems
to
be
working,
but
it's
there's
always
some
little
maintenance.
I
think
that
needs
to
happen
whether
it's
even
just
pulling
down
the
latest
code
or
you
know
updating
dependencies
when
they
change
and
knowing
that
they
changed.
I
think
there's.
A
Whoops,
I
don't
just
I
don't
know
what
happened.
Give
me
just
a
second
mural
just
went
blank
but
yeah.
That's
a
good
point.
Matt
of
yeah
also
trying
to
bake
that
into
the
user
journey
that
this
might
happen
every
time
or
not,
and
it
might
be
good
for
us
to
understand
that
on
a
average
level.
A
Is
this
something
that
I
mean?
Of
course
we
can
assume
that
it
happens
the
first
time
around
and
there's
a
lot
of
effort
there
to
get
the
development
environment
up,
but
usually
for
the
average
engineer
for
our
user
base.
How
often
does
this
happen
and
what
is
the
effort.
F
B
And
for
like,
if
open
source
is
something
you
care
about
outside
contributions,
I
mean
most
readmes
are
dedicated
to
making
it
able
to
outside
users
to
understand
what
they
would
take
to
set
this
up
in
the
hopes
that
would
get
them
to
contribute
to
it.
So
it
is
a
barrier
to
entry
to
open
source
contributions.
A
Yeah
yeah,
this
is
a
great
point
mike
maybe
you
know
from
top
of
my
head,
there
could
be
an
opportunity
to
help
project
maintainers
craft,
better,
read
me
or
structure
the
readme's
better
with
templates
or
I
don't
know
things
like
that:
yeah
great
great
thoughts,
okay,
who
else
yeah
mike
sorry,
you
were
gonna,
say
something.
A
B
I
don't
know
if
it's
cheating
or
not,
because
it's
not
about
necessarily
the
confidence
in
these
actual
stickies,
but
I
guess
it
was
lack
of
confidence
and
stickies
that
aren't
there.
B
B
Most
of
what
you
all
work
on
is
about
merge
requests
and
all
of
that's
under
the
theme
of
making
sure
the
right
people
are
checking
in
the
right
code
and
the
right
permissions
and
then
and
it's
met
the
right
conditions
before
it
goes
into
the
code
base.
And
I
don't
see
that
theme
represented
strongly
here
across
these
stickies
and
I
feel
like
that's
all
two
of
these
stage
groups
work
on.
B
A
So
you
think
that
something
so
so
that
is
that
a
that
sounds
like
more
of
a
execution
problem,
execution
of
the
user
journey
map
and
trying
to
visualize
that
and
not
so
much
something
we
need
to
do
some
research
to
inform
the
user
journey
map,
or
maybe
it's
both.
B
Yeah,
I
I
feel,
like
we
kind
of
just
need
to
add
some
stickies
in
here
and
I'm
thinking,
maybe
in
the
prepare
section
like
for
sasha
right,
probably
the
consumer
of
these
things.
You
know,
make
sure
the
proper
permissions
are
in
place
and
then
maybe
in
the
execute,
slash,
monitor
stages,
maybe
something
around
the
lines
of.
A
Yeah
there
was,
I
don't
know
if
it
was
with
this
group,
but
there
was
a
group
that
I
think
it
was
both
in
the
prepare
and
also
in
the
execute
stages,
had
something
to
do
with
the
organization's
branch
strategy,
branching
strategy,
and
so.
A
And
it
was
like
understand
the
organization's
branch
strategy
to
see
how
you
should
name
your
branches,
and
you
know
how
you
should,
where
you
should
branch
from
and
where
you
should
target
your
merge
requests
and
so
on.
So
it's
I
think.
It's
related
to
that,
and
also
the
point
or
the
moment
where
you
need
to
ask
someone
to
review,
which
has
also
to
do
with
permissions.
B
All
right,
so
what
I
mean,
what's
the
what's
the
takeaway
from
that
one
should
just
add,
try
and
add
in
a
few
stickies
or
we
are
we
past.
A
B
F
Mike,
do
you
do
you
think,
based
on
the
job
that
that's
a
thing
that
happens?
I
guess
like.
I
get
the
sort
of
argument
that
like
create
works
on
those,
but
that
I
don't
know
if
you
go
all
the
way
to
top.
I
forget
what
the
job
says.
Now
I
feel,
like
is,
do
you
think
that's
a
thing
for
coding
in
general,
or
is
it
just
really
about
like
finding
a
reviewer.
B
C
A
Thanks
mike,
I
think,
did
we
go
through
everyone
matt.
I
think
you're
missing,
yeah
right.
C
E
Okay,
yeah,
I
think
the
there's
a
couple
around.
E
Like
notifying
people
that
are
related,
that
I
were
kind
of
low
on
my
confidence
list,
so
there's
one
here
about
informing
reviewers
through
comments
yeah,
I
don't
know
if
that's
just
how
we
do
it
at
get
lab,
or
that
seems
like
that
could
be
a
more
gitlab
specific
way
of
communicating
with
people.
I
don't
know,
but
just
in
general.
A
I
was
just
gonna
say
I
think
that
makes
a
lot
of
sense.
We.
We
are
not,
for
example,
a
very
we're
not
representing
very
well,
for
example,
communication
that
happens
outside
of
gitlab
that
some
teams
that
work
in
office-
you
know-
maybe
they
have
pair
sessions
where
they're
coding,
together
or
peer
review-
or
I
don't
know-
have
a
physical
board
where
they
put
up
like
this-
is
ready
for
review
or
not,
or
using
slack
and
slack
integrations.
A
So
there
are
many
ways
to
to
do
that
and
yeah
right
now.
It's
it's
a
bit
more
gitlab
specific.
So
I
think
we
should.
I
agree
that
we
should
need
to.
We
need
to
understand
those
a
bit
more.
E
Yes
well
said
that
was.
That
was
the
main.
The
main
point
that
I
had,
I
don't
think
I
think,
there's
probably
the
other
potential
missing
thing
is
around
or
low
confidence.
We
have
some.
If
I
go
over
the
end
here
somewhere
around
create
additional
issues,
it
gets
kind
of
like
our
iteration
and
how
we
do
it.
E
A
One
one
of
the
other
groups
had
two
actions
about
creating
issues.
One
was
the
one
you
just
showed
after
the
fact,
there
was
also
another
one
about
reviewing
the
requirements
and
then
breaking
it
down
into
separate
issues,
while
we're
still
in
the
planning
phase
before
we,
you
know,
attack
the
problem.
C
C
A
Everyone
is
is
putting
their
reflective
faces
on.
You
know
like
the
thinker
from
kodan.
A
F
I
I
think
about
the
notifications
thing.
I
think
it's
it's
an
interesting
one,
because
there
were
you're
right
matt
there
was
places,
I
don't
think
mine's
mine's,
just
like
up
at
the
top.
I
wouldn't
follow
me
around.
There
were
a
lot
of
places
where.
F
Are
they
were
like
mentioned
a
few
times
like
in
terms
of
comments
and
to-do's
and
emails
and
other
things,
and
I
think
that's
a
agree.
It's
like
a,
I
would
say
I
don't
have
a
low
confidence
that,
like
notifications,
are
important.
I
think
it's
like
which
notifications
and
when
and
where
and
how
they're
delivered
is
sort
of
the
piece
that
I
have
like
a
low
confidence
on
like
what
are
the
right.
The
right
signals
there
so
yeah.
A
Yeah,
that's
great
thanks
guy,
that
that
adds
even
more
context.
I
think,
to
what
matt
was
sharing
all
right
now
that
we're
done
with
this.
So
what
we're
going
to
do
now
is
silently
vote,
and
let
me
see
how
many
things
we
have
here.
We
have
plenty,
but
since
we
have
so
many
here,
we're
going
to
limit
this
and
the
other
two
groups,
it
worked.
A
Well,
I'm
going
to
limit
this
to
just
five
votes
per
person
and
we're
going
to
vote
on
the
things
that
we
have
the
least
confidence
on
and,
of
course,
some
of
them
you've
already
heard
from
each
other,
but
we'll
vote
on
them
anyway,
and
I'm
going
to
start
the
voting
session
and
oh
and
one
thing
is
that
in
mural,
if
you
have
never
done
a
voting
session,
you
can
vote
by
clicking
on
the
stickies
and
you
can
even
add
more
votes.
A
A
Like
everything
on
on
here,
the
map-
yep,
okay,
everything
on
the
map;
okay,
so
let's
get
started.
Let
me
start
the
voting
session
at
confidence
and
five
votes
per
person,
and
I'm
going
to
give
five
minutes
for
you
to
do
that.
All
right
have
fun.
C
C
C
C
A
I
know
there
were
a
lot
of
stickies
and
that's
okay,
so
the
top
three
that
had
most
votes
were
update
dependencies
gdk
as
needed.
I
think
we
already
talked
about
that
which
is
related
to
getting
a
local
environment
set
up
and
also
to
create
follow-up
issues
as
needed,
and
those
we've
we've
discussed.
Let's
see
which
ones
we
have
new
here,
ensure
permissions
are
available
to
perform
changes.
I
think
this
is
related
to
what
mike
was
talking
about.
A
Better
issued
submission
to
make
it
easier
for
people
to
provide
details
on
reproducing.
Can
someone
talk
about
this
one?
I
don't
know
who
voted.
F
I
voted
for
it,
I
was
it
was
in
the
vein
of.
There
were
like
lots
of
comments
about
triaging
issues
or
not
comments.
There
was
like
other
stickies
about
sort
of
that
first
area
of
project
management
like
finding
out
what
issues
exist,
duplicate
issues
all
of
those
things-
and
this
was
like
a
this-
is
done
in
the
solution
or
opportunity
phase
which
is
like.
F
If
you
make
it,
if
you
get
better
inputs,
then
sometimes
all
of
those
other
things
are
potentially
easier,
and
so,
but
I
don't
know,
that's
it's
just
there.
A
Okay:
okay,
thank
you
for
adding
that
context.
Then
we
have
monitor
deployment
who
voted
on
this
one,
and
can
you
explain.
B
B
B
It's
questionable,
whether
that
is
in
any
way
connected
to
kind
of
the
create
flow
here.
Is
it
in
merge
requests?
I
don't
think
that
it
is
because
it
in
pipelines
basically
just
like
that
is
an
important
thing.
You
push
code,
especially
to
production
type
environments,
and
did
I
just
take
down
the
system
with
the
code
I
pushed,
and
we
don't
really
know
what
that
feedback
loop
looks
like
right
now,.
A
Right,
okay,
yeah,
that
makes
sense,
yeah
just
know
more
of
how.
How
do
engineers
monitor
the
deployments,
all
right,
yeah
and
anything
else
that
anyone
would
like
to
highlight
from
these
results
and
and
ask
a
question
or
or
comment
on.
F
A
That's
okay,
yeah,
exactly
cool!
So
let's,
let's
finish
this,
I
think
all
of
you
deserved.
A
Confetti
there,
you
go
whoo
yeah,
it's
one
of
the
few
times.
I've
used
this.
So
congratulations.
Thank
you
so
much
for
participating.
So
let
me
just
quickly
share
with
you
the
next
steps,
so
what
I'd
like
for
you
to
do
after
this
session
today?
If
you
have
time-
and
while
it's
still
fresh
to
share
your
thoughts
and
what
you
learn
from
this
activity
in
the
corresponding
epic
thread,
there's
there
are
two
threads
one
for
the
wrap-up
and
the
other
for
the
introduction
session
that
we
had.
I
think
a
couple
weeks
ago.
A
This
is
the
wrap-up
session
and
you
can
share
your
thoughts
here
and
also
the
intro
session.
If
you
haven't
shared
your
thoughts
feel
free
to
do
that
after
this
I'll
share
the
recording
on
youtube
and
we'll
have
the
task
of
trying
to
combine
your
user
journey
map
with
the
other
two
groups,
user
journey
maps
and
build
a
hypothesis
based
user
journey
map
for
this
job
to
be
done
in
this
persona
yeah,
and
that's
that
any
comments
or
questions
before
we
part
ways.
F
F
Okay
and
then,
once
you
have
this
combined
massive
journey
map
like
what
do
we,
what
are
we
doing
with
it.
A
Yeah,
that's
a
good
question.
What
we're
doing
with
it
is
based
on
these
voting
sessions
as
well
in
your
comments
is
to
highlight
those
themes
and
we
don't.
A
This
is
a
hypothesis
based
user
journey
map
and
we
will
turn
that
into
a
research
based
user
journey
map,
and
this
all
of
this
activity
was
to
get
the
buy-in
for
for
that,
because
it
will
take
more
work
and
to
make
sure
that
we,
you
know,
brought
down
the
walls
and
the
of
the
silos
between,
in
this
case,
the
groups
of
create
to
make
sure
that
we're
all
thinking
about
the
user
journey
and
not
just
the
features
in
our
own
groups,
I
don't
know,
does
that
help
yeah
thanks.
Okay,
yeah
good
question.
A
Thank
you,
kai,
okay,
so
before
we
part
ways
you
already
know
how
this
goes,
you
can
open
the
chat
and
I'd
like
for
you
to
share
through
an
emoji
how
you're
feeling
today,
what
is
your
mood
after
this
session?
I
think
for
most,
if
not
all
of
you
it's
morning
well,
not
for
mike.
I
think
it's
already
1
p.m,
but
yeah
share
your
mood
through
an
emoji
to
see
how
you're
feeling
and
how
others
are
feeling.
I
hope
well.
A
Okay,
eric
is,
is
festive,
I
hope
not
just
for
the
holidays.
Also
for
wrapping
this
up
kai
is
happy.
Mike
is
looking
forward
forward
to
decorating
the
christmas
tree.