►
From YouTube: Product Designer Onboarding Experience
Description
As part of the onboarding process, GitLab team members are encouraged to share their experience. Austin Regnery shares what the first month was like for him and the key learnings he took from the process.
A
Hey
everyone.
I
want
to
take
this
time
to
present
on
what
it
was
like
for
me
during
my
onboarding
process.
As
my
last
task
to
close
out
my
onboarding
issue
for
ux,
I
took
some
time
to
reflect
on
the
key
questions
that
were
presented.
I
really
wanted
to
focus
on
more
specifically
the
onboarding
experience.
A
I
recently
talked
in
our
in
our
ux
showcase
about
becoming
a
contributor
within
git
lab,
and
I
just
kind
of
wanted
to
differentiate
those
two
experiences
because
I
think
they
run
into
each
other,
but
they
were.
They
are
different
in
terms
of
what
I
was
focused
on
when
I
was
learning
at
the
time.
So
in
terms
of
when
I
was
onboarding
going
through
the
generalized
like
200
onboarding
tasks,
300
onboarding
tasks,
whatever
it
might
be,
and
incorporating
little
design
pieces
along
the
way.
A
A
A
lot
of
people
are
working
from
home,
but
more
than
ever
in
previous
roles,
I
really
do
feel
empowered
to
work
asynchronously
and
that's
made
a
big
difference
in
my
life,
even
though
a
lot
of
other
people
are
home
as
well,
I
feel
like
it's
been
able
to
help
me
really
focus
on
my
best
work
and
so
some
other
things
that
I
wasn't
necessarily
expecting.
But
I've
been
hearing
you
know
some
users
have
mixed
feelings
about
the
minimum,
viable
change
concept,
some
might
perceive
it
as
half
big
features.
A
I
appreciate
it
for
the
iteration
and
the
value
that
it
actually
brings
to
the
product,
but
definitely
it
was
kind
of
shocking
to
me
to
see
some
people
feel
like
features
weren't
fully
developed
and
they
expected
something
more
polished.
Perhaps,
but
I
still
really
believe
in
the
concept
of
how
we
ship
these
changes-
and
I
also
was
learning
that
gitlab
has
a
pretty
good,
solid
market
position.
I
wasn't
exactly
sure
of
where
we
stood
in
terms
of
our
competitors
before
I
came
in,
but
I
feel
like.
A
A
big
surprise
to
me
was
the
efficiency
of
meetings
like
wow.
We
do
not
end
meetings
late.
There
are
not
that
many
meetings
and
everything
is
gender
driven,
so
something
that
I'm
like
still
to
this
day,
trying
to
get
better
at,
is
looking
at
the
agenda
before
the
meeting
contributing
my
piece
to
it.
If
I
have
questions,
if
I
can
answer
anything
and
then
participating
during
the
meeting,
I
used
to
spend
so
many
hours
a
week
just
sitting
in
meetings.
A
A
It
was
also
really
interesting
to
see
people
talk
about
git
lab
on
reddit
or
hacker
news,
I'm
not
used
to
having
products
that
I
work
on,
be
in
the
public
eye
and
then
be
discussed
in
such
an
open
forum.
Definitely
taking
some
of
that
feedback
is
great,
but
also
it's
good
and
bad
sometimes,
and
so
you
kind
of
have
to
roll
the
punches.
If
you
will,
I
didn't
really
have
any
existential
like
big
questions
laying
down
on
me,
but
I
just
had
so
many
little
questions
and
what
was
great
about
the
handbook.
A
Was
it
answered
a
lot
of
them,
but
then
for
getting
better
context.
I
was
able
to
connect
with
my
product
manager,
my
ux
buddy.
My
own
manager,
like
getting
all
those
different
people
to
interact
with,
was
very
helpful
in
answering
those
little
things
along
the
way,
as
well
as
our
encouraged
coffee
chats
been
really
really
great.
I
try
and
do
at
least
one
a
day,
if
not
two,
but
I
limit
it
to
three
that
way.
A
I'm
still
learning
new
faces,
I'm
getting
to
meet
other
people
and
almost
every
time
I
come
out
of
coffee
chat
with
something
very
productive
about
that
meeting,
even
if
I
never
had
no
intent
for
that
to
be
part
of
the
discussion
initially,
what
I
thought
went
well
for
me
was
just
being
able
to
tackle
a
lot
of
tasks.
I
feel
like
having
the
outlines
and
the
daily
breakdown
was
nice.
A
A
I've
learned
a
lot
from
mike
and
he's
definitely
challenged
me
to
rethink
some
of
my
own
processes
in
a
way
that
will
better
the
gitlab
product
and
also
better
me
as
a
product
designer
alongside
that
man.
The
design
team
here
is
awesome.
I
am
so
inspired
during
our
weekly
showcases
or
bi-weekly
showcases,
and
getting
to
meet
everybody
and
see
what
they're
working
on
and
how
passionate
they
are.
A
It's
been
super
super
fun
to
work
alongside
that
level
of
talent,
and
I
am
very
thankful
that
we
agree
as
a
company
to
use
gitlab
as
our
main
source
for
collaboration,
like
slack,
is
like
a
secondary
thing.
Using
gitlab
has
helped
bring
a
lot
of
the
discussion
into
the
tool
and
new
features
being
introduced.
Help
encourage
that
more
so
something
I've
been
even
trying
to
learn
how
to
balance
better.
A
It's
like
when
to
use
figma
for
comments
when
to
use
our
design
management
tool
and
gitlab
for
comments,
and
what
I
found
works
well
for
me
is
when
I
have
a
discussion
that
I
want
to
bring
back
to
the
team.
That's
where
I
like
to
bring
in
screenshots
upload
them
into
the
design
management
tool,
provide
comments
there
to
create
a
good
discussion
among
the
team.
A
But
if
I'm
just
you
know
going
back
and
forth
on
like
little
design
polishing
ideas,
I
try
and
maybe
keep
those
in
figma,
because
the
designer
is
used
to
being
a
figma
and
it's
not
like
they're
getting
this
random
email
that
might
get
buried,
they're
more
likely
to
have
been
in
figma
than
my
product
manager,
my
developers,
what
didn't
go
so
well
yeah!
It's
it's
hard
to
say
what
didn't
go
well
for
me,
but
something
that
I
definitely
recognized
helped
me.
A
A
If
it's
gone
up-
and
that's
not
like
great
because
it
I
don't
necessarily
know
unless
I'm
refreshing
the
pages
frequently
to
know,
if
there's
a
new
to-do,
I
need
to
be
paying
attention
to
additionally
to-do's.
Don't
capture
everything
that,
like
notifications,
do
I'm
sure
everybody's
aware
of
this,
but
I
have
to
kind
of
go
back
and
forth
between
my
email
to
see
like
the
threads
that
I
was
following
like
what
noise
has
been
created,
because
unless
I'm
tagged,
I
don't
necessarily
know
if
anything
happened
there
within
git
lab.
A
And
lastly,
I
found
this
a
minor
annoyance,
but
I
kind
of
understand
the
differentiation,
but
there's
like
the
one
general
like
onboarding
issue,
and
then
I
have
like
a
ux
onboarding
issue,
and
so
I
found
myself
just
jumping
between
the
two
a
lot,
but
they
both
have
the
same
goal,
which
was
to
get
me
onboarded.
So
I
don't
know
perhaps
there's
some
way
we
could
create
efficient
templates
so
that
they
could
all
be
embedded
in
one.
But
I
also
appreciate
breaking
things
down
to
smaller
chunks,
so
maybe
having
two
issues
is
better
anyway.