►
From YouTube: Areas of Focus Workgroup - 2021-01-28
Description
Areas of Focus Workgroup - 2021-01-28
A
All
right,
we're
recording
yeah,
so
we'll
kind
of
repeat
the
question
just
asked
off
the
recording
any
thoughts
on
how
this
focus
group
is
going
so
far
any
thoughts
on
what
you
want
to
kind
of
what
you
are
envisioning.
The
final
goal
to
look
like,
I
think
the
method
we're
going
will
get
us
to
where
we
originally
discussed
our
end
goal
looking
like,
but
I'm
curious
if
what
you've
seen
so
far
has
changed
that
at
all
or
if
we
all
still
kind
of
think
yeah.
B
Yeah,
I
don't
think
that's
changed.
I
think
the
steps
we've
been
taking
you've
been
taking
is
you
know,
good
validation
on
the
the
the
foundation.
If
you
will
and
then
there
are
a
lot
of
things
that
can
take
place
after
that,
as
we've
talked
about.
So
I
think
the
the
end
goals
are
still
quite
valid.
Once
we
get
the
foundation
of
the
areas
themselves
agreed.
A
A
A
Cool,
I
can
tell
you
remembering
that
all
of
com,
customers,
the
the
silver
and
gold
or
sorry
the
premium
and
ultimate
sauce
customers
still
take
me
a
bit
with
emergency
service
emergency
support
running
out
of
flowing
out
to
them.
As
of
your
february
1st,
I
think
what
we're
doing
here
is
going
to
also
be
a
good
step
to
help
get
the
team
more
coalesce
so
that
everybody
can
kind
of
work
each
other's
tickets
kind
of
stop
that
separation.
I
think
it'll
really
help
us
out.
So
it's
not
oh
look.
A
C
I
actually
just
kind
of
had
a
question
around
like
in
terms
of
our
implementation,
whether
you
think
we
should
kind
of
start
working
on
that
in
parallel
like
even
though
I
know
we
don't
have
the
exact
categories
kind
of
set
out
yet
is
there
other
work
that
we
could
do
in
parallel?
While
that's
happening,
or
do
you
think
we
need
to
have
the
categories
clearly
defined
before
we
do
that.
A
At
least
in
my
opinion,
I
think
we
need
the
categories
kind
of
set
out
just
because,
like
the
routing
of
zendesk
for
that
portion
of
it,
we
need
I
mean
we
could
put
in
placeholders
like
c
d
e,
f
g,
but
I
think
it'll
get
confusing
really
quickly.
If
we
don't
have
them
game
didn't
know
what
they
are,
especially,
you
know
if
we
use
like
placeholders
in
there.
Okay,
maybe
jane
thinks
a
is
authentication,
but
I
think
it's
get
lab
features.
It's
going
to
confuse
things
as
we
try
to
do
that.
A
I
think
with
like
the
sandbox.
We
can
start
kind
of
playing
around
with
it
a
lot
more
because
it's
a
sandbox,
it's
not
production,
we're
not
really
touching
a
bunch
of
metrics,
so
I
think
we
can
start
kind
of
building
out
some
of
that
in
the
sandbox
kind
of
start
playing
around
with
concepts
which
I
mean
ideally
is
probably
where
we
should
be
testing
things
out
anyway.
A
We
know
sas
account,
which
is
its
own
view
in
its
own
form,
is
its
own
category,
and
we
know
that
free
customer
problems
are
its
own
form
or
its
own
category,
we're
pretty
sure
of
like
yeah.
Those
are
definitively
what
they
are,
because
they're
very
defined
in
zendesk
as
it
is
in
our
workflows.
So
I
think
we
could
make
start
like.
We
could
make
the
categories
kind
of
with
okay,
here's
the
three
we're
sure
of
and
then
call
them
have
a
fourth
one
for
other,
and
it's
like
right.
A
And
I
think
we
could
just
kind
of
for
for
lack
of
better
terms
iterate
on
that,
as
we
continue
to
go
with
it.
If
that's
a
direction,
y'all
think
you
want
to
go
or
if
you
think
we
should
keep
everything
isolated
to
sandbox
till
we've
got
all
our
categories.
I
guess
it's
a
matter
of
iterative
approach,
or
do
we
want
our
first
iteration
to
be?
These?
Are
the
categories
we're
going
with.
B
D
C
I
yeah
I
mean
I
would
actually
be
interested
in
seeing
like
how
it
would
actually
work
for
you
know
like
in
ic
right
where,
okay,
if
which
ones
would
I
have
access
to,
and
everyone
could
view
by
default,
and
then
you
know
how
would
it
look
like
if
I'm
assigned
to
specific
areas
right?
So
I
think
it
would
be
really
nice
to
start
kind
of
looking
at
at
the
sandbox
just
to
see.
A
The
rest
of
you
in
the
issue
be
like
this
is
what
we're
looking
at
I'll,
probably
make
a
video
to
make
it
easy
to
see
and
if
we're
all
kind
of
in
agreement,
then
we'll
get
that
into
production
as
like
our
first
beginning
place.
Luckily,
I
think
I
see
wise,
I
think
you
have.
We
have
two
placeholder
views
in
right
now.
Cynthia.
A
A
Yeah,
it's
11
because
we
could
kill
the
my
assigned
views,
but
it's
like
my
assigned
tickets,
but
it's
like
a
lot
of
our
stuff
is
pretty
tied
to
that.
I
don't
see
that
going
away.
You
get
11
views
that
you
can
see.
There
can
be
as
many
unlimited
or
there's
unlimited,
shared
group
personal.
The
problem
is,
you
only
see
11
of
what
they
call
the
shared
views,
but
a
group
view
is
a
special
shared
view
that
only
certain
groups
can
see.
C
C
Comparing,
like
you,
know
the
the
ones
that
everyone
is
going
to
see
and
then
like,
depending
on
how
many
areas
people
are
assigned
to
at
what
point
does
it
kind
of
maybe
break
down
like
like?
It
would
actually
be
good
to
see
at
what
point?
Does
it
kind
of
break
down
for
someone,
depending
on
the
number
of
areas
they
might
be
assigned
to,
and
that
sort
of
thing?
So
I
definitely
think
it
would
be
great
to
to
kind
of
get
that
testing
started.
C
A
Because
yeah,
looking
at
her
current
views,
you
know
like
that
you
would
see
as
an
ic
the
like
dot
com,
accounts
groups
and
logins.
That
view
would
be
dying
because
it's
a
it
will
become
an
area
of
focus
view.
L
and
r
will
become
an
area
of
focus.
View
sets
two
views
that
get
freed
up,
which
tells
me
in
theory,
y'all
could
be
in
three
different
areas
of
focus
at
once
before
things
will
break
at
the
fourth,
you
will
not
see
your
fourth
area
of
focus
and
that's
pending.
A
We
don't
eventually
you
know
we
don't
get
to
the
point
where
it's
like
right
now
we're
coalescing
this.
The
sauce
and
self-managed
views.
It's
like
that's,
going
to
free
up
a
ton,
more
views
so,
but
I
agree
with
you:
it'd
be
good
to
play
around
to
see.
When
does
this
break
so
we
can
have
those
day
one
we
put
it
into
production
say
this
is
where,
when
it
breaks,
I
mean
I
know,
there's
going
to
be
like
on
the
manager
side,
we'll
have
to
make
processes
for
how
long
should
you
be
an
area
of
focus?
A
Fine,
not
cool,
we
gotta
extend
it
it's
too
long.
You
know
who
knows
what
it
is.
That's
the
fun
of
iteration.
Nobody
knows,
but
yeah
so
I'll
make
an
issue
either
right
after
this
meeting
or
tomorrow,
to
get
something
set
up
in
the
sandbox
early
next
week
and
then
cynthia
you
and
whoever
you
can
get
to
volunteer
with.
You
will
help
me
test
it
in
the
sandbox.
A
A
A
The
team
of
we're
putting
this
thing
in
production,
it's
a
trial,
you
don't
have
to
use
it
right
now.
It's
us
trying
to
get
everything
kind
of
set
up.
I
think
once
we
finally
go
live
with
all
of
this.
Yes,
we're
going
to
have
to
have
an
announcement
and
processes
and
handbook
pages
and
all
that
fun
stuff.
E
Sorry,
I
missed
a
little
bit
there.
I
had
a
call
from
my
mum's
rest
time
that
I
had
to
take
so
some
of
this
might
have
already
been
discussed,
but
I'm
just
thinking
about
both
messaging
and
workflows
when
we
kind
of
get
to
the
end
game
of
this.
I
know
there
are
some
support
engineers
who
will
go.
Well,
that's
all
well
and
good,
but
how
do
which
view
am
I
meant
to
be
looking
at?
E
E
A
A
What
we
would
end
up
seeing
is
right
now,
when,
like
an
ic
is
like,
I
need
to
grab
a
ticket
for
assignment
they
go
into
that
global
view.
You
know
like
they're,
they're,
regional,
without
assignee
view,
and
they
grab
one
of
the
tickets
and
they
assign
it
to
themselves,
and
then
the
theory
is
they're
working
out
of
my
assigned
until
they
need
more
tickets.
A
The
theory
with
this
is
instead
of
going
to
that
global
non-assigned
view.
They
will
have
an
area
of
focus
view
that
is,
you
grab
out
of
there,
because
it's
your
area
of
focus
we'll
have
to
have
somebody
who
triages
them
and
to
be
like
this.
Is
this
role
and
throws
them
into
the
various
views
to
cover
the
ones
zendesk
can't
automatically
do,
because,
no
matter
how
hard
I
try,
somebody
will
find
an
edge
case.
D
A
Look
at
every
ticket-
that's
currently
in
need
of
somebody
and
going.
Oh,
I
don't
know
kubernetes,
so
I
can't
help
there
and
instead
we'll
be
I'm
specialized
in
docker.
These
are
all
the
docker
tickets.
I
can
knock
these
out
really
well
or
maybe
I'm
not
specialized
in
docker,
but
I'm
working
to
get
better.
So
I've
talked
with
my
manager
and
they've
agreed.
I
can
focus
on
docker
tickets,
so
I
can
practice
a
lot
more
on
these
tickets.
A
But
when
you
get
ready
to
pick
up
a
ticket
to
work
it
it'll
instead
be
something
that's
more
in
your
purview.
Instead
of
you
know
rolling
the
dice
on
what
you're
about
to
grab
and
my
theory
behind
all
of
this-
and
this
is
what
me
and
tom
atkins
kind
of
thought.
Is
we
looked
at
how
some
people
work
tickets.
They
know
really
well.
A
good
example
was
me
in
alaska
search
when
I
first
started
at
get
lab.
It
took
me
less
than
like
five
minutes
to
reply
to
my
last
search
ticket.
A
I
knew
it
well,
I
knew
the
approach
you
know.
I
knew
all
the
subject
matter,
whereas
somebody
who
didn't
know
it
would
have
had
to
do
a
lot
of
research,
I
could
jump
in
grab
it.
Reply
in
five
minutes
probably
resolve
it,
and
I
want
to
reply
because
I
knew
what
I
was
doing
and
then
go
grab
another
elasticsearch
ticket
and
get
it
out
of
the
way.
A
That's
kind
of
the
concept
we're
envisioning
here
is
you'll.
Get
to
the
point
where
I'm
focused
in
this
thing
that
I
know
so
well,
I
can
resolve
it
relatively
quickly
and
we'll
see
tickets
getting
resolved
a
lot
quicker.
So
in
theory
we'll
see
less
tickets
and
we
might
get
to
a
point
where
somebody
is
bored.
A
B
Yeah
so
that
so
part
of
the
burden
will
go
in
to
managers
and
ensuring
that
we're
aligned
right
with
the
number
of
people
that
we
have
in
various
areas
of
focus
and
how
that
correlates
to.
So
we
get
the
areas
of
focus
defined.
We
understand
what
the
ticket
volume
is
in
each
variable
because
in
each
region-
and
we
don't
have
everybody
in
elasticsearch,
for
example,
right
so
that'll
that'll
be
right
now,
everybody's
in
everything
and
for
the
most
part.
B
A
Yeah-
and
I
I
expect
we'll
all
probably
be
talking
with
ilya
and
lee-
to
help
us
out
on
the
metric
side
of
that
of.
Like
you
know,
we've
got
these
set
up,
it's
been
running
for
six
months,
everything's
going
well
and
lee
can
go.
Oh
man
we're
getting
a
rise
in
kubernetes.
We
should
allocate
more
people
into
that
area
of
focus.
A
I'd
like
to
see
us
get
to
that
environment.
It
also
will
help
with
like
hiring
is
something
I
could
see
benefiting
from
this
of
hey.
We
looked
at
the
tickets
and,
like
50
of
them,
are
about
kubernetes
over
the
last
year.
We
should
probably
try
to
focus
our
hiring
on
getting
someone
with
more
of
that
kind
of
experience.
B
A
Kinds
of
benefits
we
can
get
here
from
being
able
to
basically
point
to
if
we're
having
to
allocate
25
of
our
team
to
this
one
category,
let's
figure
out,
why
is
it
that
category
is
just
customers,
don't
understand
it?
Our
documentation
needs
improvement.
Is
it
there's
a
bunch
of
bugs
happening
and
we
need
to
really
you
know,
put
some
pressure
on
the
engineering
team
you'd
be
like
look
at
what
we're
having
to
allocate
because
of
this?
A
A
E
Yeah,
thank
you.
I
I
mean
I
see
massive
advantage
like
I'm
kind
of
already
taking
this
approach,
but
it's
hard
to
do
because
we
don't
have
the
areas
of
focus
when
I'm
onboarding
new
people
to
go
right.
I
want
you
to
focus
on
this
type,
get
really
good
at
it.
It
means
you
get
used
to
how
we
work
tickets,
to
have
particular
workflows,
asking
questions
and
it
will
make
yeah
even
cdps
a
whole
lot
easier
as
well,
because
I
can
actually
target
people
when
they're
learning
so
yeah.
That's
just
me
thinking
out
loud.
Thank
you.
A
A
I
mean
I
was
that
ambitious.
When
I
started
and
lyle
laughed
at
me
when
I'm
like
I'm
gonna,
learn
everything
first,
he
laughed
at
me
now,
two
years
later,
I
understand
I
laugh
at
me
too.
That
was
a
really
ambitious
goal
that
I'll
never
achieve
but
yeah
like
I
see
all
kinds
of
benefits
that
we
get
from
this
specialization.
A
I
know
I
also
liked
when
I
started
working
tickets.
I
knew
really
well
really
quickly
and
then
being
able
to
spend
an
hour
on
a
harder
ticket,
so
I
could
really
dig
into
it.
I,
but
early
on
when
I
started,
I
would
have
felt
really
bad
spending
that
hour
on
every
ticket
because
I
would
have
been
like
I
don't
feel
like
I'm
being
productive.
I
feel
like
I
should
be
pairing
with
somebody
who
will
know
the
answer
right
then,
and
there
and
I
can
move
on
with
my
life.
A
A
That's
why
I'm
glad
you're
here
cynthia
it's
good
to
have
an
ic
point
of
view
as
well
on
this,
because
me
and
tom
are
like
look
at
all
these
amazing
big
level
things
we
can
do,
and
it's
like
right,
but
this
benefits
more
than
just
the
bottom.
You
know
the
profit
version
or
whatever
it
is,
the
profit
margin
cool.
So
it
sounds
like
we're
all
we
we
all
see
benefit
in
this.
We
all
think
it's
going
in
a
good
direction.
E
A
Not
as
much
as
you
think
me
and
my
wife
are
already
talking
about
that,
I
think
the
one
he
came
to
me
with
was
about
account
like
I
know.
No
security
was
talking
about
like
an
account
deletion
thing
that
works
in
zendesk
and
my
big
pushback
was
right,
but
what
access
says
it
went
to
zendesk,
and
that
was
where
they
were
kind
of
like
we
don't
know,
I'm
like.
I
can't
say
yes
to
that
answer,
because
the
people
like
security
legal
will
tell
me
no.
A
A
Don't
be
wrong,
we'll
always
be
doing
some
work
out
of
gitlab,
because
I'm
not
going
to
figure
out
how
to
do
documentation
updates
through
zendesk.
At
certain
point,
it's
like
no
go
go
use
gitlab.com.
It
is
the
company
we
work
for
after
all,
but
yeah.
I
do
think
that
that's
a
good
kind
of
envisionment
to
have
here,
especially
because
I
know
like
l
r,
is
a
big
example
of
there's
a
lot
of
internal
issues.
I
don't
fully
understand
them,
but
it
would
be
good
to
have
them
instead
become
tickets.
B
I
think
you
yeah,
I
think,
I'm
not
sure
pipe
dream's
right
term,
but
I
think
he'll
always
be
either
in
issues
or
zendesk.
That
will
be
kind
of
the
the
long
term
right,
because
one
engineering's
not
going
to
work
on
anything
outside
of
gitlab.
So
as
we
work
into
issues
and
defects
or,
however,
we're
going
to
qualify,
those
those
are
going
to
be
in
gitlab
and
right,
our
support
engineers
are
going
to
need
to
interact,
and
hopefully
even
fix,
some
of
these
and
all
that
type
of
stuff.
B
E
My
thought
on
so
I
was
just
going
to
say
my
thought
with
internal
issues
is
the
internal
issues
that
our
customer
work.
I
totally
agree
we'll
still
work
in
and
get
that
it
would
be
really
wrong
if
we
didn't,
but
I'm
meaning
incoming
work.
And
currently
we
have
incoming
work
that
we
then
have
to
go
to
get
label
wherever
else
to
work
on
which
is
fine.
E
But
in
terms
of
where
we
receive
the
piece
of
work
that
has
an
sla
that
we
need
to
deliver
to,
or
has
a
you
know,
implication
of
an
sla
I'd
love
to
see
those
all
in
the
same
tool
set.
And
I
want
to
kind
of
remove
the
word
zendesk
from
that,
because
I
don't
want
to
suggest
that
that's
our
forever
thing,
but
that
our
incoming
work
is
all
in
one
place
that
when
a
person's
working
cues
working
incoming
work,
that's
all
in
one
tool
set.
A
Yeah,
I
know
like
I
agree
with
tom.
I
don't
think
it's
a
pipe
dream
like
I
think.
That's
something
we
very
well
can
get
to.
I
think
getting
everything
organized
like
we're
doing
with
like
these
categories
helps
a
lot
with
that,
because
then
it
starts
letting
us
see
right.
So
where,
where
are
we
straying
from
our
core
categories?
Why
are
we
straying
is,
and
a
lot
of
that
can
be?
Why
is
this
marked
other?
A
A
C
I
think
just
kind
of
to
follow
up
a
little
bit
on
what
jan
and
tom
were
talking
about.
I
I
think,
we've
already,
I
think
you've
done
a
lot
of
great
work
around
actually
doing
like
helping
kind
of
get
everything
into
at
least
sentence
so
like
with
especially
with
the
user
lookup,
and
you
know
the
sas
ticket
helper
app.
I
think,
like
building
on
those
things
and
and
kind
of
potentially
integrating
more,
whether
it's
those
same
systems
or
integrating
more
systems
like
you
know,
tom
mentions
aurora.
C
C
You
know,
that's
like
all
of
these
things
where
we're
just
kind
of
you
you've
actually
done
a
really
great
job.
I
think
in
integrating
a
lot
of
this
and
just
kind
of
continuing
to
move
in
that
direction,
I
think
would
really
help,
because
I
do
think
having
that
give
up
even
with,
even
though,
like
I
have
an
admin
account,
even
though
I
have
access
to
chat
ups
and
all
these
other
tools
to
have
it
right
in
zendesk
and
be
able
to
see.
C
Oh,
this
person
is
part
of
this
group,
and
this
group
has
this
paid
plan
has
been
like
such
a
time
saver.
I
can't
even
tell
you
how
much
of
a
time
saver
there's
a
reason
why
I
nominated
you
for
that
discretionary
bonus.
It
has
just
been
absolutely
amazing
to
see
that
and
for
other
people
and
I've
seen
so
many
other
ics,
just
kind
of
make
use
of
it
and
again,
like
the
efficiency
around
having
everything
in
in
zendesk
has
actually
been
yeah.
C
D
A
D
A
A
But
like
I
always
100
game,
even
if
it's
just
a
thing
on
the
sidebar
that
says
hey
by
the
way,
this
issue
was
just
opened
in
this
project
or
whatever,
even
if
it's
as
simple
as
that
yeah
I'm
trying
to
work
to
figure
stuff
like
that
out,
because
I'd
like
us,
like
at
least
in
my
experiences
working
in
support
as
manager
and
as
engineer
not
just
at
gitlab,
but
many
companies,
the
most
annoying
thing
is
having
to
open
50
tabs
to
do
one
ticket.
I
didn't
like
doing
it.
It
slowed
me
down.
A
Inevitably
you
forget
to
close
tabs
and
chrome
crashes
and
then
you're
really
sad
because
you've
lost.
Who
knows
how
much
work
so
like
I
I
like
the
like.
That's
I
like
being
able
to
stay
in
zendesk
when
I
have
to
look
at
something
of
like
oh
yeah,
this
user,
okay
right
here,
this
group
cool,
I
didn't-
have
to
go
run.
Curl
commands.
D
A
Look
in
the
get
lab
api
or
yeah,
so
I
think
we
can
get
to
where
everything's
kind
of
sort
of
in
zendesk
as
much
as
possible,
like
tom,
said
we'll,
always
be
working
with
gitlab
too,
because
surprise
we
work
at
gitlab,
but
I
do
think
figuring
out
a
way
to
make
gitlab
in
zendesk
work.
Well,
together
is
a
good
thing
to
do,
maybe
even
to
the
point
that
it
will
end
up
becoming
a
selling
point
for
zendesk
is
look
how
well
we
work
with
git.
A
B
C
I
just
realized
we
we've
obviously
had
a
lot
of
really
good
ideas.
Even
just
from
you
know,
your
your
prompting
of
like
here
are
all
the
things
we
we
want
to
see
and
do
right
and
some
of
it's
going
to
be
potentially
a
little
out
of
scope
of
the
the
working
group
itself
and
beyond
the
you
know,
time
frame
or
you
know,
end
goals
for
that.
A
So
I
would
say
obviously
the
out
of
scope.
Things
would
be
good
to
be
putting
issues
into
get
lab
for
support.
Ops
has
a
lot
of
labels.
I've
added
we
even
have
one
that's
called
backlog,
which
I
know
has
a
huge
connotation
to
it,
but
for
support
ops,
it
means
it's
an
envisionment
that
we
can't
do
right
now,
but
we're
going
to
look
back
on
support.
Ops
has
a
rule
of
thumb
among
or
sorry
has
a
standard
process
trying
to
use
the
right
terms,
standard.
A
At
least
once
one
toward
the
end
of
the
month
gather
everything,
that's
marked
backlog,
look
at
it
and
see
if
we
can
move
it
out
of
backlog,
our
we
have
goals
of
never
having
things
backlogged.
So,
but
beyond
that,
like
support,
team
meta
is
a
good
thing
to
make
him
in
of
like
we
have
this.
We
want
to
do
this
thing.
What
do
y'all
think?
Does
anybody
have
ideas?
A
Sometimes
there
are
people
like
in
our
support,
org
or
other
people
who
lurk
on
our
look
on
our
issue
board,
because
I've
definitely
seen
engineers
do
that
who
are
like
hey
yeah.
I
think
you
could
do
it
this
way.
Could
I
work
on
making
an
app
for
that
like
catalin's
working
on
an
uploader
app
and
he
was
like
yeah,
it's
just
something
I
wanted
to
do,
I'm
like
cool.
I
enable
you
to
do
it
if
you
get
blocked.
A
Let
me
know
so
I
would
say
if
it's
out
of
scope
for
this
work
group
make
issues
at
least
support
team
meta
or
support
ops
project,
either
way.
If
it's
in
the
scope,
I
would
say
we
put
it
in
our
dock
here
and
put
it
maybe
under
like
that
top
part
of
like
task
check-in
or
questions.
Or
you
know
things
like
that
where
it's
like
right,
let's
bring
that
up,
so
we
make
sure,
or
even
those
can
become.
D
A
B
A
What
we
work
on
and
support
ops
going
forward,
yeah
for
sure
we
do
have
a
triage
process.
If
an
issue
is
made
in
the
support
of
project
and
it's
not
tagged,
it'll
get
a
triage
label
automatically,
and
then
we
have
somebody
in
ops
whose
specialty
is
triage
or
not
yet,
but
that's
going
to
happen,
but
we
triage
those
to
give
them
labels
and
then
figure
out
how
we
can
work
them
and
all
that
fun
stuff.
Okay,.
A
Put
in
the
ops
project,
that's
it's
supposed
to
be
a
catch-all.
We
have
a
triage
process
and
ops
for
it,
we'll
get
it
placed
where
it
needs
to
be,
or
it
gets
the
supportops
category
other
tag,
which
is
my
least
favorite
tag.
I've
used
eight
times
today
all
for
issues
I
made
by
the
way,
which
makes
me
sad.
A
But
yeah
that's
that's
kind
of
a
good
starter
process
for
that
and
support
ops
is
always
willing
to
be
like
this
seems
contentious.
Maybe
we
should
talk
about
it
and
support
team
meta,
because
somebody
might
get
upset
about
this
or
we'll
blaze
ahead
and
think
something's
not
contentious
and
find
out.
It
is
later,
which
has
happened
at
least
three
times
now,.
A
A
So
if
that's
something
you're
very
interested
in
talk
with
your
manager,
because
I
basically
tell
the
ops
team:
hey
go
talk
to
the
managers
to
get
volunteers.
If
you
can't
find
a
volunteer,
it
doesn't
have
to
be
the
official
audit
either
it
can
literally
be.
I
want
to
pair
with
support
ops
cool,
just
paying
a
local
support
out
your
regional
support
office
person
and
ask
if
you
can
do
a
coffee,
chat
or
whatever
and
talk
about
ideas.
A
A
Cool
yeah,
like
literally
that's
all
you
have
to
do
in
the
ops
project.
What
you
just
did
we'll
triage
it
we'll
get
the
labels
on
it.
If
we
need
more
info,
we'll
talk
to
you
and
be
like
hey,
what's
going
on
with
this,
I
don't
quite
understand
and
for
something
like
zora.
The
first
question
I'm
gonna
be
is
so
who.
D
D
A
Stuff
like
that,
where
it's
like,
I
don't
even
know
what
this
thing
is,
how
why
don't
you?
Let's
do
a
coffee
chat,
so
you
can
show
me
what
it
is
like
ops
is
always
willing
to
do
that,
and
we
don't
need
super
descriptive
issues
to
at
least
start
with
triage,
especially
since
we're
all
tired
at
some
point.
In
the
day
we
understand
we
don't
want
to
type
up
a
book
to
ask
for
a
feature.
A
And
like
feel
free
to
share
that
idea
amongst
the
team
as
well,
I
try
to
express
to
people
of
always
come
to
ops.
If
you
have
a
question
always
come
to
us,
if
you
have
an
idea
or
100
willing,
I
also
acknowledge
that
I
sometimes
look
like
I'm
angry
and
that
may
intimidate
people
I've
gotten
that
feedback.
A
E
E
C
I,
since
you
mentioned
that
anything
in
scope
we
should
have
at
the
top
of
the
dock.
I
did
just
add
some
of
the
things
that
we
just
talked
about
today
in
the
task
list
and
partially
I
put
them
here
because
I
I
think
these
are
things
we
should
address
as
we
create
issues
for
for
them,
then
we
can
link
them
to
issues,
but
some
of
these,
I
think
we
probably
want
to
address
later.
A
Oh
yeah
and
like
the
stuff
at
the
very
top
of
that
doc,
the
idea
is
that
static
stuff,
so
we
don't
have
to
search
for
it
so
stuff
that
we
want
to
keep
like
up
there
that
it's
like,
like
the
task
list.
Cynthia
just
put
that
or
like
this
is
the
work
group
page
that
I
could
I
forget,
where
it's
located
all
the
time
and
after
google
at
least
20
times
a
week,
yeah
stuff
like
that,
definitely
top
of
the
page
static
stuff.
A
D
A
A
Cool
I'll
take
that
as
a
no
remember
to
encourage
everyone
you
see
in
support
to
fill
out
that
survey
I'll
probably
make
another
post
about
it
tomorrow
in
the
team
chat
and
put
something
in
the
support
we
can
review.
If
it's
not
there
already
reminding
people,
especially
now
that
the
form
is
fixed
and
doesn't
require
you
to
fill
out
a
second
option
but
definitely
encourage
everyone.
You
see
to
be
filling
that
out,
because
we
really
want
that
data.
We
want
to
be
sure
our
categories
are
good.
Amongst
the
vast
majority
of
the
team.