►
From YouTube: 2019 10 24 Weekly Sync
Description
Knowledge Group Weekly Meeting
A
B
C
A
D
A
So
so,
basically
Kristin
the
way
it
works
is
the
first
person
in
the
meeting,
and
that
is
between
myself
and
rank
I.
Whoever
comes
first,
it's
recorded
to
their
computer
and
then
I'm
gonna
pull
over
record.
It
it'd
be
nice
if
they
just
upload
it
to
get
lab
on
filter
to
the
knowledge
group
channel.
But
Chi
is
Kristin
in
that
administrator
group
that
she
added
so
that
if
she
shows
up
first,
she
can
do
that.
I
have.
D
B
Needs
to
happen,
it's
like
someone's
you,
yeah
Kristen,
should
probably
cancel
the
Siri
well,
I'll
say
two
things:
one.
The
knowledge
Siri
does
like
Ceres
doesn't
need
to
happen
at
this
time
like
anymore
right,
like
you
guys,
coulda,
just
based
on,
like
the
new
group
of
people
acknowledged
like
without
me,
being
there
right
to
a
different
weekly
synced,
a
different
weekly
UX
sync
timeslot
I
would.
A
B
Being
mindful
of
the
fact
that,
like
ondrea's
and
all
of
them
and
has
source
code
on
Monday
and
Tuesday,
and
not
an
editor
on
Wednesday,
select,
we
kind
of
gets
it.
There
is
taken
like
that's
the
day,
but
like
the
meetings
can
be
adjusted,
I
think
what
should
happen
is
like
I,
think
I
created
the
knowledge
calendar
I
created
the
original
ones.
The
invites
and
the
zoo
meetings
are
linked
to
my
zoom
account.
I
would.
C
B
D
D
C
C
C
So
what
I
mean
by
this
is
that
unless
you,
unless
you
disagree,
I
think
12:6
will
be
a
little
bit
still
slim
on
feature
capacity
because
we'll
have
detected,
but
from
12
7
onwards.
We'll
have
much
more
capacity
for
future
work,
and
the
idea
here
is
that
there's
so
many
things
that
are
affecting
the
day
to
day
work
that
if
we
don't
fix
them
now,
it
will
be
even
bigger
problems
later
and
I'm
compiling
the
list
of
things
that
we
should
address
and
I
mean
it's
all
about
building
that
up,
but
closer
to
the
date.
C
I'll
have
concrete
issues,
2.2
weights,
that
sort
of
thing
and
enology,
and
then
we
can
talk
a
little
bit
about
a
this
feature
could
really
really
needs
to
go
into
12
6
and
we
can
find
capacity
and
that
sort
of
thing
but
I
from
now.
My
point
is
just
to
give
a
heads
up
that
we're
thinking
about
doing
a
more
heavy
tech
debt
release
on
12
6
than
usual.
But
since
we're
gonna
have
double
capacity,
you
might
not
really
feel
it
but
yeah
that
was
my
heads-up
and.
C
The
first
for
the
first
three
weeks
or
so
and
they'll
be
working
on
small
issues
and
that
sort
of
thing
to
get
acquainted
with
the
codebase
and
yet
for
the
first
couple
of
milestones,
there
will
be
slower,
but,
for
example,
if
we
give
them
like
refactor
work,
that
I
really
did.
That
is
really
well
specified
and
in
plan,
and
we
give
them
an
intro.
They
will
still
be
slow,
but
they'll
be
getting
acquainted
with
the
codebase,
much
quicker
because
they're
touching
several
parts
of
the
code
base,
but
yes,
I
do
it.
C
C
C
I
have
to
check
I
it's
around
20.
He
should
be
around
20
at
this.
At
this
point
we
will
I
what
I
usually
do
is
like
I'll
ramp
them
up
from
like
60
to
70%
on
the
first
cycle,
then
the
second
I'll
put
them
up
to
100,
but
so
I'll
wrap
them
up
in
terms
of
capacity,
but
I
have
to
play
with
time
off
as
well.
But,
yes,
the
the
overall
capacity
of
the
team
should
go
up
to
20
some
things.
A
C
B
D
C
A
D
A
D
So
the
next,
the
next
one.
This
is
just
a
general
question
in
terms
of
the
team
and
just
I've
kind
of
I
guess
the
next
two
questions
go
together,
but
I'm
just
kind
of
opening
up
the
floor.
If
you
guys
have
any
questions
about
the
products
that
we're
delivering
and
also
like
the
process
that
we
use
as
a
team
and
just
I
sort
of
start,
the
conversation
we
don't
have
to
go
through
it
today,
but
one
of
the
things
that
I'm
kind
of
learning
as
I'm
onboarding.
D
If
we
can
aim
to
get
that
release
ahead
of
engineering
and
really
make
it
our
goal
like
me
and
Jarrett,
to
fully
flesh
of
these
issues
so
that
you've
got
everything
you
need
to
sculpt
it,
including
almost
like
mandatory
designs
on
every
single
issue.
Even
if
it's
just
like
a
screen
shot
with
an
arrow.
D
That
would
really
help
me
get
these
into
these
workflows.
That
they're,
looking
at
now
and
in
the
PM
work,
which
shows,
as
you
take
an
issue
from
beginning
to
end,
and
you
really
do
go
through
a
design
phase
and
the
UX
team
is
that's
their
part
of
it.
But
we
just
as
a
team
I'm,
just
wondering
if
you
guys
have
any
feedback
on
that
or
thoughts
on
it
and
incorporating
the
design
flow
into
our
team.
And
what
what
you
guys
think
about
that
I.
C
C
But
then
code
wise,
you
might
require
a
really
big
refactor
and
they
can
identify
that
right
from
the
start.
So
my
oh,
my
my
my
concern
always
goes
to.
If
we
split
them
up,
will
it
be
like
the
old
days
where
we
just
like
throw
a
prototype
over
the
wall
and
if
you
like
coding
alone,
that
I
really
don't
want,
but
apart
from
that,
I,
don't
really
have
a
problem
with
having
these
these
two
phases.
If
we
can
manage
that,
but
I
would
rather
have
some
someone
assigned
to
that
queue.
D
D
I
think
that
just
having
that
goal
to
be
to
have
all
these
discussions
really
fleshed
out
before
you
guys
actually
put
scope
on
and
I'm,
also
just
empowering
Jarek
to
kind
of
run.
The
show
in
terms
of
this
is
what
we're
doing.
This
is
why
this
is
the
users
pane.
This
is
how
we're
addressing
it
here
are
three
or
four
ways
we
could
address
it
now,
let's,
like
talk
about
why
we
chose
option
three
and
just
saw
a
whole
team,
gets
it.
A
All
right,
I,
would
say,
I
think
it's
a
good
idea
to
do
that,
because
I
find
a
lot
of
times
we
kind
of
get
way
down
and
then
maybe
the
technical
discovery
or
discussing
it
or
or
implementing
something.
And
then
the
question
comes
up
well,
do
we
need
this?
Who
said
we
needed
this?
Why
do
we
need
this
and
you
do
spend
a
lot
of
time
explaining
that
answer
or
we
go
to
UX
and
then
ask
them
to
kind
of
justify
why
we're
inhuman
in
your
door?
A
Time
in
discussion,
and,
of
course,
if
they
need
support-
or
they
have
to
ask
someone
a
question
whether
it's
backing
or
fronting
we're
available.
But
if
it
turns
out
that
you
just
don't
even
want
something
that
can
save
us
a
lot
of
work
early
on
right
or
they
want
something
else
that
we
didn't
think
about.
For.
D
Sure,
or
we
can
validate
it
with
some
kind
of
mock
up
right
like
Jarek,
you
can
do
a
clickable
if
it's
a
big
feature,
a
clickable
usable
prototype
that
no
one
has
to
code,
and
we
can
actually
get
it
in
front
of
our
users
too
and
see
what
they
think
before
we
even
touch
code
on
some
of
those
bigger
ones.
Obviously,
yeah.
E
Think
it
would
be
interesting
to,
depending
on
like
you're,
saying,
scope
of
what
we
might
be
looking
to
ship.
We
could
utilize
that
milestone
to
do
different
types
of
research
depending
on
the
scope.
So
if
it's
something
small
we're
adding
to
the
UI,
we
could
say:
okay,
because
this
is
a
small
piece
of
the
UI.
We
can
do
a
clickable
prototype
or
hey
we're.
Looking
at
a
new
section
or
a
new
process
for
design
management,
you
know-
maybe
we
should
look
at.
E
You
know,
take
a
further
step
back
at
a
broader
view
and
do
more
just
in
general.
You
know
questions
or
you
know,
tap
tap
UX
research
to
do
that
process
and
I
would
love
to
you
know.
Collaborate
with
everyone
here
to
you
know,
put
together
sort
of
that.
What
that
process
looks
like
okay,
we're
starting
the
milestone.
We're
gonna
start
looking
into
this
particular
piece
and
then
like
what
do
we?
D
A
A
D
D
Learn
more
about
it,
like
you,
shouldn't
have
to
like
read
an
encyclopedia
to
understand
what
you
get
when
an
issue
is
handed
to
you
so
like
just
having
those
concise
summaries
relates
to
this
research
relates
to
this
epic,
like
just
some
really
high
level
stuff
to
sort
of
you
can
rock
it
immediately.
Yeah.
E
D
A
D
And
I
think
sometimes
and
I'll
have
to
I'm
just
getting
going
so.
I
haven't
really
done
this,
but
I
think
just
a
short
summary
that
I
could
do
after
having
read
50
comments,
and
just
summarize
it
there's
so
much
discussion
over
X
number
of
months.
Here's
what
we
deduced
from
that!
Here's
like
what
we're
gonna,
do:
here's,
what
we're
not
and
why
TLDR
yeah.
D
D
So
I'll
do
my
best
as
I'm
learning
these
as
I'm
getting
up
to
speed,
I'll
try
to
TL
DR
as
much
as
I
learn
as
I
go,
which
it's
a
new
process
for
me,
because
I'm,
where
I
worked
before
it
was
a
much
smaller
company.
I
was
essentially
writing
what
we
were
gonna
do
it
wasn't
like
it
was
coming
up
through
all
the
comments,
so
I
got
to
learn
that
I'm
being
here,
I
get
lab,
but
yeah
that's
really
good
feedback
and
then
the
other
thing
that
I
was
considering
and
just
thinking
is,
if
Jarek.
D
If
you
can,
we
can
talk
about
this
later,
but
if
you
can
even
present
to
us
to
our
team
prototypes
in
envision
and
figma,
one
or
the
other
or
both.
So
we
can
like
interact
with
you
so
where
our
team
is
getting
also
just
that
knowledge
of
how
those
tools
work,
because
that's
really
the
space
that
we're
in
so.
E
A
C
Would
be
particularly
useful
for
me
in
probably
the
engineers
as
well,
because,
like
we
know
about
these
tools,
I've
heard
about
them
ever
since,
like
me,
the
first
ones
that
showed
up,
but
we
don't
use
them,
we
don't
know
the
flows.
We
don't
know
how
they're
evolving
and
I've
seen
figma
announcing
things
like
every
week
or
whatever
so
you'll,
be
good
to
us,
keep
tabs
on
what
they're
doing
and
to
learn
from
them
as
well.
I.
D
Think
that
would
be
sweet
and
I
know.
Jarek
Christi
told
me:
you
guys
can
pick
any
tool
and
that
gets
expensed
either.
So
you
get
to
do
whatever
workflow,
but
I
shall
let
you
buy
them
all,
essentially,
because
you
need
to
really
be
up
to
speed
in
that
space
yeah,
but
I
think
that
would
be
awesome
for
our
empathy
for
our
users
as
well,
and
just
seeing
how
the
whole
process
works.
Yeah.
C
In
terms
of
in
terms
of
strategy,
this
is
more
of
a
product,
but
one
of
the
things
that
I
think
we'll
never
be
able
to
compete
with
is
like
direct
competition
with
figma
or
something
like
that.
But
it
could
be
useful
first
identify
spaces
where
they're
not
being
able
to
deliver
like
we
having
like
you,
Kristin
you've,
mentioned
that
in
previous
call.
Like
those
things
we
can
do,
that
they
can't
do
it's
gonna
be
very
beneficial
in
knowing
what
they're
doing
and
then
how
we
can.
Oh
there
we
go
yeah.
D
So
this
I
mean
this
is
so
rough.
This
is
not.
This
is
not
like
published
anywhere,
but
this
is
how
I've
been
seeing
it
as
I've
been
learning
from
issues
and
just
throwing
things
visually
on
to
this
sketch
comp,
but
yeah
I
would
say
that
right
now,
here's
what
we've
done
right.
We
posted
designs
to
an
issue
or
getting
design
feedback
and
revision
history,
essentially
on
each
of
those
static
assets
that
were
uploaded
and
that's
the
space
like
envision
essentially
plays
across
the
whole
board,
but
envisioned
in
figma.
D
We
can
be
a
player
in
that
sense
of
presenting
designs
and
approving
them
on
an
issue.
What
we
don't
want
to
get
into
is
being
sketch
or
being
and
vision
or
saying
that
there's
only
one
way
to
do
it
or
get
into
this
design
system
company-wide
design
systems,
which
is
local
on
your
Mac,
where
that's
what
the
marketing
team
like,
how
they
set
their
logos
and
everything
I,
don't
think
we
want
to
even
touch
that
space
but,
like
you
may
have
seen
like
in
that
other
call
that
does
developer
handoff.
D
They
would
show
up
on
like
hacker
news
or
design
news,
because
it's
just
such
a
different
type
of
feature
I
haven't
seen
anyone
do
that
yet
and
of
course
we
could
do
some
of
these
other
things
too,
like
versioning
of
your
sketch
files,
we
simply
does
like
we
could
put
a
repo
on
a
local
sketch
file,
which
is
what
are
you
Xers
do
behind
the
scenes,
but
I
think
the
part
that
it's
getting
me
excited.
Having
read
a
lot
of
the
backlog,
it's
just
this,
the
handoff
like
the
Timmy
having
done
UX
having
done
front-end.
E
D
D
I
showed
this
to
my
boss
in
my
one-on-one,
and
he
thought
I
was
saying
we
were
gonna,
just
sort
of
like
destroying
vision,
figma
everything
like
the
way
that
arrows
go.
It's
not
very
clear
so,
like
it
doesn't
eat
I.
Think
another
revision
of
just
saying
you
could
flow
your
designs
through
envision
to
get
lab.
These
arrows
are
kind
of
lame
right
now,
yeah.
C
Maybe
maybe
we
were
too
biased
because
we're
in
we're
in
the
we're
in
building
the
tool,
but
with
the
way
I
see
it
is
like
we
have
to.
We
have
to
provide
like
a
value
to
the
user,
for
them
to
even
come
on
and
then
yeah
and
we'll
be
able
to
pull
them
into
stuff
that
we
not
only
us
will
be
able
to
pull
off
like
the
visual
review
app
that
sort
of
thing,
if
we
don't
give
them
a
place
to
discuss
and
improve
designs,
why
would
they
be
even
here
so
I'm?
C
E
D
E
Always
been
one
of
my
core
philosophies:
is
their
core
function,
your
core?
What
you
do
should
be
absolutely
killer.
It
should
be
like
you
know,
top
level
and
then
all
the
other
features
outside
of
that
can
sort
of
this.
They
come
secondary
to
making
the
very
core
feature,
absolutely
phenomenal.
Yeah
yeah.
C
I'll
just
add
that,
from
the
front-end
perspective
like
be
uploading,
right
now
is
pretty
much
at
the
most
basic
level.
We
can
definitely
do
a
lot
more
work
there
and
improve
that
I
think
it
comes
like
this
is
the
this
was
the
MVC
of
uploading
so
to
speak,
but
we
didn't
every
as
we're
having
more
space
and
we
have
that
with
who
has
covered
like
the
basic
corners
that
we
need.
C
We're
gonna,
get
to
revise
that
and
do
a
much
better
upload
that
you
don't
have
to
have
a
maximum
of
10
designs
per
up
per
batch.
Other
thing
that
to
me
kind
of
feels
weird
is
like
having
the
file
name,
be
the
canonical
ID.
So
if
I
could
just
be,
I
mean
a
design
and
I
could
just
like
upload
a
replacement
regardless
of
the
file,
and
it
seems
like
something
but
I.
Don't
know
that
I'm
pretty
sure
you've
seen
this,
but
Marcel
is
working
on
this
plugin
from
sketch
directly
tricks
port.
So
it's.
C
Because
we're
from
when,
when
Marcel
was
explaining
that
to
me
it
was
telling
me
I
mean
if
it's
an
easy
thing
for
me
to
put
my
designs
into
get
lab,
then
I
might,
but
if
it's
hard
and
I
have
to
go
out
and
export
them
and
then
go
on
the
website
and
drag
them
and
then
wait
10
by
10.
Yes,
it's
painful!
So
all
of
those
things
you
can
really
make
a
difference,
but
but
yeah.
So,
interestingly,.
E
D
D
D
Put
Marcel
on
right
now,
while
he
was
talking
but
yeah
craft
is
what
you
use
to
post
your
local
sketch
files
like
I'm
in
sketch
here
right
now,
if
I
had
craft
running,
I
could
go
like
this
click
and
hit
hit
a
one
time
button
that
would
show
up
here
and
it
would
go
to
envision
in
one
click
like
someone
would
tell
me
a
revision.
I
would
do
it,
I
would
hit
it
and
it
would
be,
it
would
be
live
in
a
second,
so
we
will
move
among.
D
E
C
A
B
D
But
we
could
that
plug-in.
That's
that
would
be
like
a
local
Mac
plug-in
that
would
connect
your
sketch
to
get
glad
it's
not
on
the
official
road
map,
but
I
just
threw
it
here,
because
it's
the
same
as
what
Kraft
does
and
I
think
it
would
be
really
important.
I
just
didn't
prioritize.
It
I
was
like
a
next
focus,
but
if
he
gets
it
to
a
point
where
it's
like
almost
there
I
feel
like
we
should
loop
this
in
and
like
make
it
an
official
get
lab
plugin
for
such
that
make
sense.
It's.