►
From YouTube: Kickoff Meeting: Information Architecture Refresh
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hey
everyone
just
recording
just
in
case
people
can't
make
it
so
I
set
this
meeting
up
a
little
last
minute.
I
really
appreciate.
I
appreciate
your
availability
and
ability
to
get
here.
I
planned
it
to
be
earlier
next
week,
but
I
popped
onto
cindy
blake's
calendar
and
it's
qbr's
next
week,
so
I
was
like
oh
no,
there's
no
availability.
So
that's
that's!
Why
we're
a
little
bit
late
or
I'm
a
little
bit
late
in
getting
the
invite
out
so
purpose
of
the
meeting?
A
Just
a
quick
kick
off
for
this
information
architecture
refresh.
I
covered
a
lot
of
this
in
our
group
conversation
and
I
have
a
video
walking
through
the
what
and
the
why-
and
I
wanted
to
get
this
group
together
primarily
to
have
single
points
of
contact
for
elements.
That's
in
our
in
the
agenda
here.
So
I'll
just
share
that
real
quick
of
like
what.
What
is
this?
Why
are
we
here?
What's
going
on
so
the
goal
in
simplest
terms
make
the
marketing
site
smaller,
it's
so
big.
A
So
that's!
This
is
just
like
a
fancier
way
of
saying
that,
with
more
words,
roles
and
responsibilities
again,
this
is
just
my
first
take
on
it
happy
to
iterate,
but
I
was
thinking
jess
leading
the
design
of
this.
I
know
jesse
and
I
worked
on
a
whole
bunch
of
this
kind
of
work
in
the
past
and
you
led
the
redesign
of
the
navigation,
so
you
I
just
felt
like
you
popped
into
mind
here.
A
Lauren,
obviously
I
mean
you're,
the
you're,
the
engine
of
our
team,
and
I
figure
having
your
skill
set
in
terms
of
full
stack
engineering
and
knowing
the
pipeline
is
gonna,
be
really
valuable
when
we
figure
out
how
we're
gonna
make
make,
I
don't
know
I'm
trying
to
avoid
using
the
word
dev
site
like
I
feel
like.
A
We
need
to
build
the
thing
beside
the
thing
and
then
just
you
know,
take
the
railway
tracks
and
point
it
at
the
new
one
content
so
cindy
and
val
and
oh
yeah
value
you
made
it
and
sandra
as
well.
A
Adam
brandt
asset
needs
alliances,
still
trying
to
figure
that
out.
I'm
gonna
check
in
with
colleen
greco
and
see
who
she
recommends
niall
for
seo
francis
the
competitive
pages
that
we're
going
to
have
customer
reference,
jen
and
laura
and
then
alex
to
keep
that
ecommerce
mindset
and
also,
I
know
you
have
this
superpower
of
like
using
salesforce
and
getting
weird
data
sets
connected
in
a
really
valuable
way.
So
you
you
popped
into
mind.
A
Starting
off,
like
you're,
jumping
on
a
freight
train,
that's
kind
of
what
I'm
hoping
this
whole
experience
is
like.
Like
I
have
a,
I
haven't,
been
able
to
think
of
a
nicer
term.
So
if
there's
like
little
kid
ears
in
in
the
vicinity,
I'll
say
it
quietly.
But
the
theme
I
was
thinking
for
this
group-
is
we
don't
talk?
We
do
like
this
needs
to
be
really
action
oriented
it's
a
very,
very
short
timeline.
A
We
have
time
to
iterate.
We
have
time
to
talk
things
through
and
make
sure
we
do
it
right,
but
I'm
always
concerned
with
big
kind
of
ambiguous
projects
like
this,
that
the
talking
overtakes
the
doing
and
then
every
day
we're
talking,
puts
more
pressure
on
the
doing
I'll
pause
there
open
it
up
for
for
some
conversations
or
input.
B
I
just
made
a
quick
note
there,
michael
too,
and
this
is
something
we
can
discuss,
but
christina
weiss
has
been
mentioned
as
potentially
being
part
of
that
content
team.
So
that
might
be
something
to
that.
We
can
discuss
like
val
and
cindy
and
stuff
just
to
just
to
make
sure
that
we
know
exactly
who
who's
doing.
What.
C
You
you
can
count
on
it
being
me,
I
don't
know
if
she's
gonna
get
involved,
but
at
the
higher
level
yeah
just
gonna
say
you
don't
need
like
50
content.
People
on
this
call
is
my
point,
so
you
might
as
well
go
with
me
as
the
starting
point,
because
I
I
have
visibility
into
both
content
marketing
and
the
blog.
A
Sounds
good
thanks,
val
awesome,
yeah
and
like
we'll
we'll
have
a
working
group
like
we'll
add
more
people?
Okay,
I
said
working
group,
I'm
actually
doing
everything
I
can
do
to
avoid
using
that
terminology
working
group
because
there's
like
a
whole
list
of
things
you
gotta
go
through
and
set
up
another
like
handbook
page
which
not
against
handbook
pages,
but
I
do
feel
like
we
have.
A
I
I
worry
about
creating
a
second
source
of
truth,
so
we
have
this
epic,
and
this
has
everything
that
would
be
on
that
handbook
page.
So
I
don't
know
what
I
call
this
like
our
working
team
as
single
points
of
contact.
A
So
if,
if
I
need
to
talk
to
somebody
about
brand,
I'm
gonna
go
talk
to
to
adam,
I'm
not
expecting
adam's,
the
one,
that's
gonna
whip,
open,
figma
and
make
the
thing
we
need,
but
we
just
know
who
to
talk
to
to
get
the
action
that
we
need
in
the
slack
channel
information
architecture
refresh,
we
can
add
everybody
who's
gonna
be
working
on
this,
like
my
entire
team,
is
focused
on
this.
This
quarter
this
and
brand
rollout-
I
thought
really
hard
yesterday.
Should
we
be
talking
about
brand
rollout
like?
A
Should
that
be
the
same
project
and
I'd
like
to
have
a
division
between
those
projects,
because
getting
this
done
means
we
have
a
smaller,
more
contained,
manageable
experience,
that's
going
to
make
it
way
easier
to
roll
out
the
brand.
So
it's
a
it's
not
a
hard.
This
then
that,
but
this
work
really
makes
that
work
a
lot
more
manageable,
so
yeah.
I
I
also
don't
expect
to
have
like
a
a
weekly
or
bi-weekly
meeting,
that's
kind
of
what
I
wanted
to
get
into
in
process.
A
D
Just
a
quick
question
in
terms
of
you
just
mentioned:
restrained
timelines
for
development,
and
it's
going
to
happen
this
quarter,
so
just
from
an
seo
perspective.
I
just
wonder
because
I
know
one
of
the
the
main
priorities
is
to
reduce
the
overall
bulk
of
the
site.
So
from
from
the
perspective
now,
have
you
got
a?
Is
it
a
system
where
you
have
identified
pages
already
you're
thinking
of
reducing
from
the
map
or
is
it?
A
That's
a
good
question:
I
don't
have
a
super
thorough
answer.
Basically,
what
I'm
thinking
is,
if
it's
not
on
this
list,
it
could
be
removed.
Now,
for
example,
I
want
to
move
away
from
this
idea
of
topics
I
I
would
love
us
to
start
saying
category
leadership,
it's
the
same
thing,
but
I
know
we
have
excellent
results.
Page
one
for
devops,
as
of
yesterday,
saw
that
message
loved
it.
A
I
know
that
the
way
we
get
there
from
seo
perspective
is
we
have
devops
and
we
have
some
child
pages
that
are
supporting
that
we're
not
getting
rid
of
those
like
I'm
not.
The
goal
here
is
not
to
knock
everybody
out
at
the
knees
because
for
simplicity,
but
I
am
going
to
put
pressure
on
pages
that
are
in
existence
that
aren't
really
driving
anything.
D
Yeah,
so
usually
the
process
for
that
is
like
we'd,
so
there's
certain
pages
that
might
be
driving
anything,
but,
for
instance,
they
might
have
a
lot
of
backlinks,
but
somehow
they
fit
into
the
structure.
D
So,
ideally,
what
we
do
is
audit
the
site
and
come
up
with
a
list
of
pages
that
can
be
so
they're
kind
of
working
back
from
a
number,
because
what
we'll
find
is
a
lot
of
the
pages,
for
instance,
you
might
have
pages
that
have
good
ranking
for
something
but
low
traffic,
which
means
that
would
be
an
optimization
target
instead
of
a
cooling
target
or
other
instances.
So
we'd
have
to
use
specific
data
points
to
identify
what
is
valid
to
be
called.
D
So
we
might
come
near
a
number
like
that
is
the
target,
but
it's
safer
to
use
this
process
to
identify
what
can
be
removed
or
redirected
instead
of
taking
chunks
out
of
the
site
and
then
later
seeing
kind
of
tanks
and
traffic
or
or
some
kind
of
impact
down
the
road.
It's,
I
suppose,
just
data
back
decision
making
makes
a
little
bit
safer
and
easier
of
a
process.
A
Agreed
data
is
gonna
win
the
day.
We
can't
have
a
motion
in
this
project.
A
A
Okay,
so
getting
into
just
like
the
tactical
how
how
we
work,
what
would
be
most
optimal?
I
just
added
some
links.
You
know
we'll
add
the
people
working
on
this
work
in
this
channel.
We
have
this
okr
that
I
just
shared.
I
put
everybody
in
here.
We
can
adjust
this
as
we
go
along
we'll
create
issues
out
of
this
epic
so
and
manage
the
work
through
there.
A
A
High
level
you
can
see
here,
it's
monday,
the
sprint
begins.
We
do
sprint
planning
which
you
can
see
here
wednesday.
We
do
an
async
sprint
release,
so
we,
what
we're
trying
to
do
is
minimize
the
amount
of
meetings
maximize
the
amount
of
time
we
have
to
work
on
things.
So
here
we
say
hey.
This
is
what
we're
shooting
towards
this
is
what
we
want
to
release
by
next
wednesday.
A
We,
you
know,
do
our
work.
Have
our
heads
down
monday,
we
kind
of
start
popping
a
few
message
in
slack,
you
know
with
our
confidence
level
or
any
changes,
we're
making
to
what
we're
going
to
release
based
on
our
progress
and
then
thursday
you
can
see
here.
We
do
a
sprint
release,
video
celebrating
what
we
did
and
then
a
retro
which
is
just
what
went
well,
what
could
have
gone
better?
How
are
we
gonna
keep
getting
better
at
that,
so
my
goals
like
why
why
this?
It's
really,
I
just
want
visibility.
A
I
want
us
to
be
able
to
all
see
what
everybody's
working
on
and
then
coordination,
and
if
we
can
work
in
this
way,
then
we
can
add.
We've
got
a
couple
boards
built.
I
would
love
to
be
able
to
add
everybody
who's
relevant
and
doing
work
within
our
digital
experience
project
here.
What
we're
looking
at
is
our
current
sprint,
our
current
iteration-
and
this
is
our
whole
team's
in
here.
So
we
can
see
what
everybody's
working
on
I'd
love
to
see.
A
You
know
everyone
who's
contributing
to
this
work,
have
a
board
in
this
project
so
that
we
are
aware
of
who's
working
on
what
who
needs.
What
oh,
did
I
put
the
same
link
there?
I
think
I
put
the
same
like
what
was
I
actually
trying
to
do
there
current
planning,
okay,.
A
Yeah,
and
then
this
this
is
this-
is
everything
all
up
so
not
broken
into
by
person.
This
is
really
useful,
for
you
know
craig
and
other
people
who
are
just
keeping
an
eye
on
all
of
the
work
that
we're
doing.
We
can
see
some
weight
points,
so
it
just
gives
gives
visibility
into
what's
being
worked
on
or
like
what's
coming
and
what's
doing
so,
what
we're
actively
working
on?
C
E
A
A
Let
me
go
back
to
this
I'll
share
my
screen
again.
A
I
could
see
I'm
going
to
pick
on
francis
just
because
you're
first
over
here
and
it
your
involvement,
I
believe,
is
content
related
as
well.
So
I
could
see
an
issue
or
an
epic
look.
Maybe
there's
a
sub
epic
to
this
epic
for
the,
why
git
lab
pages
and
then
in
there
there
are
issues
for
the.
Why
why
gitlab
over
github
there's
a
design
issue?
A
So
I
could
see
that
what
I
need
from
content
people.
You
know,
let's,
let's
talk
about
a
category
leadership
page
so
devops
we
have
this
page,
but
we
need
it's
gonna
retain
primarily
a
lot
of
the
awareness
level
stuff
that
it
does.
But
there
could
be
a
change
like
we
could
need
a
little
bit
of
change
in
the
content
or
we
could
need
a
new
image
here.
So
we
would
write
issues
for
those
needs.
A
We've
been
trying
to
do
this
in
the
past
and
having
some
challenges
with
getting
brand
assets
and
content.
Historically,
I
know
just
you
and
I
have
been
working
on
trying
to
get
improvements
there.
So
once
these
issues
are
there
and
they're
assigned
to
an
individual,
you
know
about
them.
You
know,
and
we
can
see
that.
Okay,
you
know
val's
working
on
this
or
she's
got
this
on
her
to-do
list.
A
In
this
sprint
we
can
expect
that
she
will
either
move
it
forward
this
sprint
or
give
us
an
update
that
I
I
know
that
this
is
on
my
list.
I'm
moving
this
into
the
next
sprint
cycle
because
of
xyz.
So
it's
really
for
very
specific
needs.
Nothing
like
no
big,
like
like
strategic
sort
of
like
stuff.
It's
it's
for
output.
D
I
think
just
to
point
to
one
of
the
things
in
terms
of
the
topics
pages-
that's
already
kind
of
pipelined.
So
much
of
what
we
do
with
the
with
the
devops
page
is
pipelined
over
the
coming
months
for
all
the
all
the
topics
pages,
as
well
as
additional
pages
that
are
going
to
be
needed
for
the
new
solutions
launch
and
such
as
that,
so
that
kind
of,
like
would
have
been
overlapped
there,
maybe
I'd,
say.
A
Awesome:
well
then
we
could.
We
have
a
I'll
show
you
this
other
thing
we
made,
because
this
is
like
a
common
gotcha
using
git
lab,
especially
amongst
many
many
different
projects
and
the
fact
that
our
code
base
what's
nice
about
this
buyer
experience
is
the
code
base
is
in
the
same
project
but
in
the
in
www
areas.
So
we
have
this
template,
which
is
just
really
like
a
a
directional
template.
A
A
This
is
not
where
this
work
is
happening,
but
by
making
this
issue,
it's
now
being
tracked
on
this
board
as
part
of
this,
this
initiative
so
definitely
not
interested
in
getting
people
to
do
things
twice.
Just
trying
to
add
some
product
management
principles
around
coordination,
to
make
sure
that
we
have
visibility
and
we're
tracking
towards
a
successful
outcome.
E
So
I
have
another
question
and
forgive
me
if
this
is
sort
of
off
topic,
but
I'm
not
sure
I
I
know
what's
going
on
in
our
team,
I'm
not
sure
what's
going
on
in
other
teams,
but
I
know
over
the
you
know,
past
12
to
24
months.
We
have
requested
updates
to
certain
pages.
Is
part
of
this
calling
and
reshaping
of
these
pages
going
to
incorporate
I'm
assuming
other
teams
have
made
similar
requests,
those
updates
to
like
for
us.
I
know
the
dreaded
us
saying
we
want
this
slash
customer's
page
updated.
A
Potentially,
I'm
very
happy
that
we
didn't
make
those
changes,
because
that
would
have
led
to
rework.
We
have
an
excellent
brand
refresh
project
going
on
we're
very
close
to
doing
doing
that.
If
you
look
at
this
issue,
you
can
look
at
the
little
legend.
10
pages
is
what
you
know.
What
good
looks
like
I'm
trying
to
push
us
to
like
15
to
20
pages
with
the
new
brand
roll
out.
A
So
if
you
look
through
this
you'll
see
the
little
star
or
if
you
look
through
the
spreadsheet
or
the
table,
you'll
see
if
the
page
is
considered
able
to
deliver
the
brand
rollout.
So
on
the
customer
case,
study
pages
that
is
not
planned
at
this
time.
E
Understood
so,
as
far
as
what
you'd
be
asking
for
us
and
apologies
again,
if
this
is
reiterative
of
what
you've
just
said,
are
we
expected
to
go
and
determine
what
pages
need
content
updates
or
are
y'all
as
you're
updating
these
going
to
create
those
issues
and
tag
us
in
to
request
that
that
reference
content,
yeah.
A
A
Leadership
and
brand
perspective
like
it
is
more
like
everybody
together,
but
in
my
experience
it's
typically
the
you
know
when
you're
looking
at
the
blueprint
of
the
page,
it
becomes
pretty
obvious
that,
like
this
is
the
behavioral
economics
of
the
page
and
how
we
should
communicate
the
customer
reference
team
input
was
also.
A
I
would
love
your
input
on
like
in
solutions.
We
have
a
by
industry
section
and
I
thought
of
y'all,
because
you
know
you,
you
know
the
actual
customers
and
the
content
like
the
use
cases
and
wins
that
then
we
could
kind
of
surface
into
this
section
as
well.
So
that's
that's
like.
I
think,
where
a
lot
of
your
intelligence
could
really
help
us.
E
E
F
Yeah,
so
that's
where
we
would
need
a
lot
of
content
help
something
that
doesn't
exist
already.
We
need
content
for
we're,
not
just
calling
down
when
it's
there,
but
trying
to
like
rethink
some
things
as
well.
So
there
are
some
like
brand
new
pages
and
to
I
think,
jennifer's
point
earlier.
We
can
definitely
tag
you
in
things
that
we
need
content
for,
and
I
think
if
we
do
that
on
it,
that
nile
is
talking
about
at
first
of
like.
F
E
A
A
G
In
the
course
of
the
design
of
these
pages
make
it
so
that
when
content
needs
to
go
in
and
update
like
like
niall-
and
I
just
did
with
the
devops
page-
that
it's
much
more
straightforward
to
content-
you
know
than
what
we
kind
of
found
with
the
devops
page,
which
had
been
hyper
designed.
So
we
had
to
kind
of
jury
rig
around
it
to
get
in
our
updates.
A
Yeah,
I
mean
everything
totally
and
thinking
past
this
project.
Things
that
this
opens
up
for
us
is.
We
have
a
smaller
experience.
Less
pages
makes
it
a
lot
easier
to
add
a
cms
to
everything.
C
A
Everybody's
problems
having
something
that
works
like
it
should
have
worked
10
years
ago,
so
I'm
with
you,
my
thinking
on
this
is
deadline,
usually
dictates
what
we
can
deliver.
So
yes
to
everything
and
then,
when
it
comes
to
what
can
we
deliver
by
that
that
deadline?
Then
that's
when
prioritization
comes
in,
so
I'm
not
I'm
not
saying
no
to
it
yet,
but
we
may,
as
a
group,
need
to
say
no
and
not
in
terms
of
no
it's
more
like
not
right
now,
but
okay,
I
definitely
I
want
to
get
to
that
future.
State
too.
A
H
I
think
that
where
she's
had
it
is
you
and
I
have
talked
to
michael
about
you
know,
I
used
to
be
able
to
maintain
my
own
solution
pages
and
then
the
web
team
changed
stuff
and
I
couldn't
even
find
where
it
went,
found
it
then
and
was
able
to
to
do
that
the
content
changes
some
of
that
changes
kind
of
frequently,
especially
things
like
customer
references
that
or
you
know
assets
we
want
to
drive
people
to
or
whatever,
and
not
that
we
want
to
redesign
the
page,
but
we
may
need
to
add
some
things
or
tweak
a
message
if
we've
done
some
research
to
find
that
something
needs
to
be
updated
or
what
have
you
and
having
the
ability
to
do
that
without
asking
mother
may
I
is
super
important
to
keep
us
from
having
a
bottleneck.
A
Right.
Okay,
so,
let's
that
this
this
theme
is
governance.
Governance
is
not
part
of
this
project,
but
it
is
I'm
hearing
it
as
something
that
that
is
a
quick
follow
like
we
can.
While
this
work
is
happening,
let
me
let
me
think
through
that
and
how
we
can
get
the
right
people
to
come
up
with
this
governance
and
I
think,
as
a
marketing
org
like
we
need
to
align
on
it.
C
I'm
not
I'm
just
going
to
say,
though
we're
all
all
on
the
same
team
here.
C
Is
it
governance
or
is
it
simply
access
because
the
I
just
want
to
say
super
excited
to
see
our
devops
page
hit
page
one
and
google,
but
you
know
it
took
sandy
and
niall
three
hours
to
make
the
updates,
because
of
the
way
that
the
page
is
constructed.
Yet
you
know
you
have
to
do
little
bits
at
a
time
and
it's
just
that's
just
not
efficient
make
sure
you
didn't
break
anything
like
you
know.
C
A
In
terms
of
so
what's
an
analogy
I
can
use
like
supply
chain
comes
to
mind.
What
we're
doing
is.
We
are
using
better
ships,
we're
using
bigger
warehouses.
A
First,
that's
going
to
have
the
greatest
impact
and
the
biggest
business
value.
Then
what
we're
going
to
do
is
we're
going
to
move
the
things
around
within
the
warehouse.
So
if
we
find
out
like
oh,
if
I
move
the
the
bolts
to
the
right
and
the
screws
to
the
left,
that
means
we
can
make
changes
faster.
C
Yeah,
I
have
a
quick
follow-up,
so
I
see
and
I'm
blind,
as
is
obvious
right,
where's,
the
where's,
the
blog
and
all
this.
On
your
like
on
your
list
of
things,
I
didn't
actually
see
the
blog.
A
In
the
right
column,
the
very,
very
right
column,
okay,
third,
from
the
top
resources,
docs
blog.
A
H
A
We
will
do
that
collectively.
I
don't.
I
don't
have
an
answer
for
that,
yet
I
I
start
very
ambiguously,
I'm
very
comfortable
in
ambiguity
it.
It
requires
a
lot
of
trust
from
the
group
and
a
lot
of
enrollment.
So
I
I
ask
for
patients-
and
I
also
can't
figure
it
out
on
my
own-
that's
why
we
need
this
single
point
of
contact
group.
Give
us
give
us
this.
A
We
just
started
a
sprint
on
monday,
it's
full
of
like
non-related
stuff
to
this,
but
if
you
can
give
like
me
and
jess
and
lauren
just
this
till
next
week
to
kind
of
wrap
our
heads
around
just
like
the
core
of
what
we
need,
we
can
come
back
to
the
group
and
say:
okay,
we've
we've
made
things
a
little
bit
more
clear,
like
here's,
how
we
see
next
steps?
How
does
this
feel
to
everybody?
H
H
Let's
make
sure
that
we're
aware
and
conscious
of
what
the
product
team
has
and
not
duplicating
their
pages
because
they
are
marketing-ish,
they
have
videos
on
how
to
use
it.
What
it
is
it
to
me,
it
bleeds
into
marketing
a
lot
more
than
most
product
pages.
Would
that
are
because
it's
maintained
by
the
product
managers,
not
pmm,
but
just
to
bring
that
up
and
make
sure
everybody's
aware
that
those
are
there.
H
You
know-
maybe
it's
just
a
matter
of
navigating
to
them,
or
maybe
it's
a
matter
of
putting
some
guidelines
and
asking
them.
If
hey,
when
you
do
these
pages,
could
you
include
xyz
or
what
have
you
but
food
for
thought.
A
Yeah,
we'll
we'll
sort
that
out,
I
think
we're
at
time
like
right
at
time
so
feel
free
to
drop
if
you
have
to
but
yeah
we'll
we'll
take
it
all
in
we're
going
to
take
it
all
in
we're
going
to
make
the
best
decisions,
then
we're
going
to
do
what's
right
for
for
our
experience,
but
thanks
everyone
thanks
for
being
open
to
jumping
in
this
call
so
quickly.