►
From YouTube: Wrike Training with Nabil
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
A
A
No,
no
one's
in
hang
out,
okay
cool
all
right,
so
we
have
six
of
us
and
we're
recording
it.
Okay,
perfect
all
right!
So
let
me
share
my
screen.
We'll
get
started
so
I'm
assuming
everyone
is
onto
here.
It's
curious
to
figure
out
how
mic
works.
I've
written
up
a
couple
short
bullets
to
kind
of
walk
through.
At
the
same
time,
if
people
want
to
consider
how
small
we
are,
we
can
also
just
do
like
a
Q&A
as
well.
So
let
me
share
my
screen.
A
Cool
all
right
vane
wants
to
follow
along
as
well
I'm.
A
To
walk
through
the
various
topics,
so,
if
you
hear
you're,
probably
already
have
logged
in
and
access
right,
so
essentially
it's
set
up
quite
similar
to
how
slack
was
set
up.
So
you
have
the
hierarchy
of
groups
and
things
on
the
left
and
the
hierarchy
of
Reich
is
spaces
which
is
essentially
a
large
area
of
like
project.
So
you
could,
you
can
imagine
you
know.
I
have
my
own
space.
I
can
set
up
a
separate
space,
for
example,
for
the
design
team.
A
That's
shared
with
us,
and
everything
inside
was
owned
by
us,
and
no
one
else
has
access
to
it.
So
it's
kind
of
like
a
working
environment
for
separate
teams.
We
are
yet
to
have
multiple
spaces
for
that
purpose,
considering
how
small
we
are,
but
that's
the
highest
group
level
that
you
have
been
ranking
next,
you
have
folders
and
folders
are
just
dumb
buckets
speckle
that
hold
various
things
inside
them.
So
in
this
case
this
app
folder
calls
to
projects
inside
of
it.
A
This
taps
folder
those
three
projects,
keycard
holds
to
project
and
and
we'll
get
to
the
swarm
you
later,
but
that's
essentially
the
next
level.
So
those
spaces
projects,
and
then
you
have
spaces
folders,
and
then
you
have
projects
now,
projects
are
where
work
actually
starts
to
have
to
get
assigned
to
people,
and
you
start
to
get
responsibilities
and
actual
work
being
done
so
in
the
first
two
levels:
spaces
and
folders.
This
organizational
structure
projects
correlate
actual
output
of
things,
so
we'll
use
status
to
be
ones
in
it
as
an
example.
A
Actually
it's
a
bit
of
a
complicated
when
we
find
a
simpler
one
here
on
mobile
on
desktop,
you
are
not
related
to
the
v1
wrong.
It's
its
own,
separate
thing.
It's
you
know
launching
the
desktop
UI,
that's
right,
the
mobile
UI
on
desktop.
So
what
is
contained
in
this
project
is
a
bunch
of
tasks
and
potentially
some
sub
projects
and
bugs
which
kind
of
sit
in
here
at
the
separate
container.
A
So
this
entire
project
contains
tasks
and
subtasks,
and
each
task
needs
to
have
one
owner.
This
might
be
an
easier
way
to
see
mobile
and
desktop.
This
is
the
project,
there's
no
timelines
here,
but
you
can
kind
of
see
everything
that
encompasses
this
particular
project,
so
spaces
folders
projects
and
then
tasks
and
subtasks
I,
don't
know
there
any
anything
with
sub
tasks
here,
but
you
can
imagine,
create
an
XLS
package.
I,
don't
know
who
who's
only
there's,
maybe
Pedro,
but
what
you
could
then
have
is
you
can
say.
A
So
that's
the
first
kind
of
high-level
overview
now.
The
other
thing
to
note
is
that
every
well
best
practice
is
that
every
single
project
and
every
tasks
should
have
an
owner.
Someone
is
responsible
for
it.
So
in
the
case
of
status
v1
the
owner
is
myself.
You
have
acceptable
wallet
experience.
You
have
Rachel
each
one
of
the
subtasks.
This
is
Andre.
This
is
ma
che.
No
one
is
responsible
for
approving
transaction
history.
The
eric
is
responsible
for
this
one
and
it,
and
so.
B
A
So
forth,
so
everything
has
a
person
responsible
and
what
that
helps
to
do
we'll
see
it
later
is
when
you're
doing
things
like
reporting
and
analytics.
You
can
see
if
someone
is
kind
of
overburdened
with
with
work
that
needs
to
be
done
and
things
like
that,
so
every
project
and
every
task
and
subclass
should
have
an
owner
all
right.
So
that's
that
project.
Well,
that's
the
hierarchy
of
stuff.
Any
questions.
A
Is
it
a
little
bit
doesn't
have
as
much
information,
and
it
obviously
is
very
time
it's
very
again.
Trunk
centric-
and
sometimes
this
is
not
what
I'm
interested
in
I
have
I
haven't,
really
used
board
or
a
table,
but
I.
Think
yesterday
you
guys
use
the
board
of
view
if
a
design
stuff
is
that
correct
or
you
attempted
to
no.
B
B
A
Cool
there
you
go
and
I
guess
board.
It
helps
to
visualize
like
what
is
being
worked
on
these
issues
at
TiVo
Kanban
board
stream
is
interesting
because
you
can
see
all
the
work
done
within
this
given
project
or
folder,
and
so
I
personally
use
that
for
so
looking
at
my
own
stuff,
I
look
at
stream
of
everything
that
shared
with
me
to
comment
and
I,
that's
kind
of
like
my
mental
workflow,
so
you
can
say,
what's
everything
that's
happened
inside
of
status?
V1
is
here
time
long?
A
We
don't
really
use
that
you
can
use
that
if
you
want,
but
no
one
kind
of
does
and
I
I
really
like
analytics.
So
you
can
see
all
the
tops
have
been
created.
Everything
that's
being
worked
on
all
the
major
milestones
who
is
most
overburdened,
so
you
can
see
here
like
you
have
Andre
designer.
It's
got
like
a
ton
of
stuff
to
work
on
right.
A
So
maybe
that's
not
like
a
lot
of
the
projects,
maybe
need
to
be
re
prioritized
because
this
doesn't
seem
scalable
right,
and
so
you
can
kind
of
see
that
here
you
can
tells
you
where
there
are
conflicts
between
some
individuals
milestones.
This
is
an
interesting
one.
I
know
as
as
we
flesh
out
timelines
it'll
be
interesting
to
see
how
its
duration
thing
looks
because
you
know
to
the
complete
status
v1,
it's
4,100
hours
of
work.
What
does
that
like?
A
Considering
everyone
that's
working
on?
It
is
that
kind
of
was
that
is
that
add
up
properly
like
we
ask
them
anything
correctly
anyway.
So
if
you
have
projects
a
sign-
and
you
have
that,
like
dates
for
the
amount
of
work
done,
is
even
needed
for
human
project,
this
analytic
stuff
becomes
super
useful.
So
those
are
the
the
main
views
that
I
find
for
projects
list
or
table
Gantt
chart.
A
There's
a
Gantt
chart
I
find
it
helpful
at
times
when
I'm
trying
to
understand
like
okay,
how
how's
project
updates
going
and
so
I
could
usually
look
like
this.
Since
a
works,
has
it
been
working,
one
hasn't
worked
on,
but
in
terms
of
using
this
on
the
back
often,
this
is
much
easier,
also
to
add
tasks
to
add
subclass.
It's
just
easier
to
see
everything
like
this
any
comments
or
questions
on
the
views.
B
A
A
Critical
path,
so
this
that's
right.
This
critical
path
button
just
highlights
things
that
are
going
to
be
the
long
pole
in
in
the
entire
project.
You
can
go
into
I,
don't
know
which
one
it's
got
like
details
there,
something
like
mobile
performance.
You
can
see
that
this
bug
face
is
going
to
be
the
long
pole
of
development,
and
if
you
start
adding
dependencies,
then
those
those
will
get
highlighted.
So
you
can
see
again.
This
is
the
thing
that's
going
to
take
the
longest
and
therefore,
if
this
slips.
A
You
can
view
it
like
this
in
terms
of
when
things
get
started
well,
interesting
view
and
but
without
accurate
timelines
and
start
or
end
dates.
These
of
use
to
become
a
meaningless.
So
assuming
that
the
older
dates
and
applications
and
who's
working
on
what
are
correct,
then
actually
this
becomes
super
powerful
in
this
case,
like
I,
can't
really
tell
you
can
see
names
here,
but
I
can't
tell
who's
been
assigned
to
certain
things.
So
from
about
performance
when
I
go
to
listing
you,
you
can
actually
see
like
okay.
This
stuff
is
being
worked
on.
A
This
is
being
completed
and
you
can
see
what's
not
being
assigned
to
certain
people,
so
it's
just
easier
to
it
to
follow
things
along
this
way.
For
me,
I
guess
the
others,
while
we're
looking
at
this
one
other
view
that
I
think
is
super
useful,
oh
and
we're
gonna
sing
a
lot
in
I.
Guess
I
may
be
happening,
get.
A
A
A
All
right
so
moving
on
the
next
thing,
so
we
have
these
multiple
spaces
and
right
now,
we've
set
up
three
spaces
based
on
one
being
a
swarm
view
of
the
world
and
this
kind
of
highlights
responsibilities
and
kind
of
workflow.
That's
being
done
in
this
one
way,
you
can
see
here
core
UI
token
economics,
key
card
and
multi
account,
seeing
instead
of
keyword,
etc.
A
So,
if
you're
looking
at
things
from
a
swamp
perspective
or
funding
perspective,
this
is
that's
how
this
is
set
up
now
for
me
personally,
it's
easy
to
view
the
world
in
a
project
view
because
I
think
of
them
in
terms
of
one
on
discrete
launches,
so
I
created
a
separate
space
where
you
have.
This
is
that
these
are
very
steps,
and
this
is
keycard
stuff,
and
these
are
projects
for
the
particular
like
a
given
bones.
That's
coming
up
right,
I
picked
like
these
were
just
seven
different
projects.
A
I
picked,
there's
nothing
logical
about
why
these
are
the
ones
that
were
talking
for
mine.
So
if
there's
other
projects
that
exist,
you
could
just
put
them
in
your
create
a
new
folder
here.
Point
being
is
that
this
something
like
telling
network
v1,
it
exists
here
in
the
gaps
folder
and
also
in
three-two-one
telenet
work.
A
So
this
tagging
I
feel
like
makes
it
very
easy
to
be
quite
fluid
and
we
don't
need
to
have
Richard
you
like
Jesus
matrix
structure
is
this
and
that
it's
like
well
there's.
This
is
a
given
body
of
work.
This
thing
needs
to
launch
this.
Is
the
team
that's
responsible
for
it,
and
this
is
how
we're
gonna
track
it
like
this,
and
you
know
we
can
use
tagging
to
make
things
be
easier.
We
can
also
do
this.
Like
is
that
design
related?
Yes,
we'll
add
up
to
the
design.
A
You
know
design,
swan-like,
I,
think
that
or
if
there
could
be
a
design
space,
you
could
also
have
it
there.
So
this
tagging
system
is
super
powerful.
One
thing
for
okay,
so
these
are.
This
is
a
project.
You
want
a
swarm
view
of
the
world.
The
final
space
that
we
have
is
all
our
github
repository,
so
I've
seen
I,
think
there's
nine
now
and
they're
all
here,
because
a
bug
or
an
issue
needs
to
sit
with
the
in
the
github
repository
within
the
folder
for
it
to
be
regularly
synced.
A
Now
what
we
can
do
is,
let's
say
resolving.
Lint
errors
is
going
to
block
the
launch
off.
Now
it's
going
to
block
the
launch
of
the
mobile
on
desktop
today,
WI,
you
can
just
you
go
in
here.
You
find
a
bug.
The
search
feature
works
pretty
well,
so
you
could
just
search
for
it,
but
then
you
come-
and
you
say.
C
A
Assigned
to
someone
inside
of
github,
which
I'll
come
to
a
bit
later,
then
it'll
also
mirror
itself
here
to
the
right
person.
And
then
you
have
you
know
the
Gantt
chart
view
of
resulting
wind
errors,
and
you
can
say:
listen
it's
here,
you
can
say
well,
it's
gonna
take
this
long
to
do
whatever
to
result
in
errors
and
now,
in
30
seconds,
we've
managed
to
get
this
Quito
issue
and
it
will
still
be
synced
both
ways.
So
this
this
timeline
I,
think,
will
come
up
inside
of
github,
I,
think
and
yeah.
A
C
B
A
Actually,
it
lives
inside
of
the
bug
fixing
swarm,
so
you
could
also
say
well.
This
is
super
important.
It
should
be
part
of
say
status.
We
would
you
assign
it
here
this.
You
see
the
red
line,
that's
actually
something
that
I
manually
did
so
you
go
here.
You
say:
color
I
made
it
red
because
it's
important
I
made
the
downs.
One
green
I'll
make
the
DEP
store
long
in
this
portal,
and
it
just
makes
it
easier
to
kind
of
follow
things
alone.
There's
no
logic
to
it,
so
yeah.
A
A
Sense
I
mean
I've
I've,
only
been
using
rock
for
a
couple
of
weeks
and
I've
only
had
one
training
session
of
my
own
and
I
was
very
high
level,
so
I'm
kind
of
commenting
without
formal
training
on
this
stuff
and
as
things
change
or
we
become
better
acquainted
and
feel
free
to
comment
or
update
the
right
usage
in
status
talking
for
things
to
be
more
accurate,
or
this
is
a
better
way
of
doing
things,
because
yeah
we're
relatively
unique
in
how
our
organisation
is
structured.
So
we've
made
this
fit
into
our
structures
cleanly
as
possible.
B
I'm
not
sure
what
else
you
have
planned,
maybe
thinking
of
the
perspective
people
in
the
call
it
would
make
sense
to
kind
of
go
through
what,
if
I
want
to
add
a
new
task
like
maybe
someone
has
an
example
of
a
new
task.
They
want
to
add
so
we've
got
sort
of
all
like
okay.
This
is
like
adding
the
timeline
for
it.
This
is
assigning
someone
for
it
to
see
what
I
mean
on
the
block.
A
Okay,
cool,
that's
a
great
idea
so
because
you
can
tag
things
across
multiple
places,
you
can
add
it
anywhere
you
like,
so
you
could
come
in
here
and
you
can
say
I'm
inside
of
browse
improvements
in
this
video.
So
you
just
create
a
new
task.
Call
it
browse
improvements,
meaning
this
resolution.
I,
don't
know
I'm
just
sort
of
been
done,
but
let's
say
me
and
Ezra
resolution
b2,
so
you
create
a
new
task
at
assignee,
locally
rachels
on
this
call
so
she'll.
A
She
won't
be
surprised
by
this.
Okay
sweet.
Actually,
so
you
said
yeah,
so
you
can
set
a
beginning
day.
You
can
send
it
an
end
date
and
then
you
can
make
it
so
task
is
like
and
the
UI
and
the
other
thing
is
back-end.
Whatever
you
can
attach.
Files
I
can
assign
it
to
multiple
people.
I
can
then
assign
it
to
the
core
UI
swarm,
which
is
here.
A
A
Then,
when
work
started
on
it,
you
come
in
here
and
you
say:
work
in
progress.
Then
we
give
it
a
Gantt
chart
view
or
browser
improvements,
and
we
can
see.
Okay,
here's
some
work,
that's
being
done
on
in
this
resolution,
be
I
could
go
to
the
core
UI.
If
I
wanted
to
like.
If
I
want
to
view
everything
like
this
I'd
go
to
the
core
UI,
so
on,
then
I
can
see.
A
A
Yeah,
so
this
is
on
Rachel,
these
subtasks
aren't
anyone's
I
could
be
like
well,
this
sub
task
is
sure
actually
go
to
Hester,
but
then
this
one
should
go
to
I,
don't
know
who's
on
this
code.
I
don't
want
to
compute
anyone,
but
you
put
it
on
to
Julian
or
something,
and
obviously
the
sub
task
then
can
then
have
further
sub
tasks.
You
could
then
have
a
start
and
end
date.
So
at
least
there's
you
could
have
like
it
ends
in
infinite
nest
of
tasks
and
subtasks
I
live
inside
of
project.
The.
A
Element
is
like
every
task
needs
to
have
an
owner
and
the
rule
of
thumb
that
we've
used
and
this
you
can.
You
can
follow
this
or
you
don't
have
to
is
like
if
it's
over
ten
hours
work
so
roughly
over
one
day
at
work,
you
should
put
it
in
right
if
you
want
to
use
this
as
your
like
day-to-day
to-do
list,
checklist
go
ahead,
but
that's
a
good
rule
of
thumb
is
like.
If
it's
over
a
day's
worth
of
work
over
times
would
work.
Hopefully
you
should
live
inside
of
here.
A
So
I
still
could
break
this
up
into
like
create
prototypes
great
wireframes,
whatever
whatever
or
just
leave
it
like
this
and
then
in
progress
completed.
And
then,
if
we
come
to,
we
look
at
browser
improvements
and
we
want
to
see
who
is
working
on
what
in
browse
improvements,
you
can
say
well,
there's
a
whole
bunch
that
is
being
worked
on
it's
on
the
critical
path
and
who
owns
it.
Much
owns
a
bunch
of
it.
Much
is
completed
most
of
them
and
Gantt
chart
view,
etc.
C
B
C
D
A
A
C
A
Let's
say
he
needs
to
be
done,
start
okay,
so
you
can't
you
can
set
length
of
time.
I,
don't
know
the
answer
by
the
way
I
figured
out
on
the
fly.
If
you
want
I
think
you
have
written
a
comment,
but
in
the
right
usage
dock
there's
like
a
list
of
questions
that
some
of
them
resolved
some
happened.
You
want
to
write
your
question
down.
I'm
hoping
to
have
my
next
like
Rachel,
Hester
and
I
are
doing
training
with
the
right
people,
and
then
we
can
awesome
this
specific
question.
B
B
A
A
We
need
to
it
doesn't
show
me
how
many
days
but
I
know
wait.
Okay,
what
point
being
gay
will
fool,
try
and
figure
out
how
to
do
it?
The
one
thing
I
didn't
mention
we
kind
of
quickly
went
pasta
is:
are
these
states
so
you
have
in
progress
completed
on
old
canceled.
Quite
often,
we
have
a
lot
of
work
for
each
team
that
is
not
being
actively
work
on
like
that
becomes
that
would
just
put
on
hold
and
then
that's
it
and
it
can
stay
on
hold
until
actually
gets
assigned
to
someone.
A
A
If
you
indent
is
so
tossed
making
it
a
task
of
sub
tasks,
you
all
you
need
to
do
is
indent
it
and
that
will
live
inside
of
this
DNS
resolution
v2.
So
the
final
work
is
here
so
then
this
you
are
Muslim
is
blocking
the
front,
work
and
key
card,
and
then
you
have
another
task
or
called
public
launch
or
milestone.
A
There
we
go,
I
can
convert
it
to
a
milestone,
that'll
sit
somewhere
and
the
friend
work
and
key
card
integration
are
dependent
and
I'm,
assuming
his
red
line
means
that
you
can
start
to
see,
match
dependencies
and
say
this
won't
launch
until
these
things
happen.
If
you
like
views
like
this,
then
obviously
the
Gantt
chart
view
is
helpful
and
then
this
is
all
then
reflected
also
in
the
list.
So
you
can
see
these.
All
things
are
being
worked
on.
A
A
A
Software,
like
you
know,
I,
feel
like
the
investment
is
very
rarely
results
in
significant
quality
output,
in
this
case,
I
think
it's
very
smooth
to
use
and
like
the
simplicity,
money
and
tossing
assigning
to
people
I
just
feel
like
it
does
help,
especially
considering
we
distribute
a
team.
We
can't
sit
around
a
whiteboard
every
week
and
kind
of
a
look
at
the
same
thing.
In
this
case,
we
can
get
some
really
interesting
insights
and
find
out
who's
being
overburdened.
Who
has
been
with
things
like
that?
A
A
D
A
A
A
D
A
Sweet
all
right,
so
my
bad,
but
now
all
three
should
be
people
should
be
able
to
see
it
for
now,
I
would
avoid
creating
new
spaces
just
so
that
we
don't
have
bloat
of
information
that
my
evarin
has
access
to,
but
I
think
as
we
mature
in
the
usage
of
this,
then
it
might
make
sense
for
us
to
start
doing
that.
First
for
certain
tasks.
A
If
people
are
doing
things
that
are
sensitive
to
other
parts,
for
example
like
quarry,
if
you're
doing
something
on
the
security
side
that
you
don't
want
anyone
else
to
see,
that
is
where
it
makes
sense.
Danny
the
same
on
the
finance
side,
we
can
have
separate
spaces
for
sensitive
things,
but
yeah
I
think
that's
been
primarily
what
the
various
spaces
are
used
for.
A
C
A
If
they
have
contributed,
I
think
it
appears
in
their
stream
I
think
if
there's
explicitly
CC,
it
appears
in
their
inbox
and
they
get
an
email
about.
It.
I
also
think
that's
customizable
per
individual
because
you
can
get
bombarded
with
the
kind
of
emails
that
can
use
this
correctly.
I'm
still
having
100%
figured
out
how
all
the
different
notifications
work,
because
I
don't
know
what
tasks
I'm
assigned
to
sorry.
A
A
A
So
if
I've
commented
and
then
someone
comments
after
me-
maybe
I
don't
get
it
email
notification
but
maybe
does
appear
on
my
stream.
So
the
way
I
why
I
use
it
so
far
is
that
I
log
in
and
I
check
my
inbox,
which
here
Correa's
sees
evening
on
this
and
then
I
check
my
screen
stream
to
see
what
has
happened
and
what's
been
worked
on
that
and
you
can
see
everything,
I
follow
or.
A
D
D
A
D
A
A
D
B
D
A
D
Right
also
like
there
are
two
artifacts
one
is
about
the
problem.
Another
one
is
about
fixing
this
problem
and
it
looks
like
both
should
live
in
the
corresponding
project,
but
then
like,
like
okay,
if
I
will
add
the
buck,
it's
just
for
for
everyone
to
be
notified
that
this
bug
is
a
part
of
project
that
it
will
be
fixed,
yeah
actual
work
again,
it's
poo
request
that
okay
I
fixed
it
and
then
something
whatever
someone
fixed
it
some
tester
would
tested.
D
D
A
A
Anna
anyone
else
any
other
comments,
otherwise
I'll
probably
schedule
another
kind
of
walkthrough.
If,
if
we
feel
like
we
need,
though,
people
wanted
in
a
couple
of
weeks
once
become
even
more
familiar
with
everything,
otherwise
I
would
recommend
just
locking
in
like
blocking
out
two
hours
and
playing
around
with
stuff
and
doing
what
I
did
just
make
it
fake
issues
and
take
things
moving
around.
You
just
get
a
feel
for
it
and
it
becomes
very
intuitive
yeah.
For
me,
this
is
like
a
project
management
version
of
Slackware.
A
A
Of
work
and
structure
should
kind
of
be
like
a
one-off
that
you
do
and
then
everything
else
should
be
what
I
made
it
so
is.
This
is
taking
up
a
lot
of
your
time.
Please
let
me
know,
because
that
the
goal
is
not
to
just
do
work
for
works
sake.
The
goal
is
to
try
and
basically
give
visibility
on
on
what
is
being
worked
on,
and
then
the
most
important
thing
is
like
what
is
the
critical
path
for
us
to
launch
this
v1?
How
does
that
look?
What's
the
timeframe?