►
From YouTube: Team knowledge-sharing - Universe 2022
Description
Presented by: Cassidy Williams
As your teams grow, so does your collective knowledge of all that you've built together. Managing and documenting that knowledge can be daunting, but it's so important for remembering decisions, creating new ideas without reinventing the wheel, and bringing new teammates up to speed. In this talk, Cassidy will discuss strategies for taking (and finding!) notes as a team.
As always, feel free to leave us a comment below and don't forget to subscribe: http://bit.ly/subgithub
Thanks!
Connect with us.
Facebook: http://fb.com/github
Twitter: http://twitter.com/github
LinkedIn: http://linkedin.com/company/github
About GitHub
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Millions of people use GitHub to build amazing things together. For more info, go to http://github.com
A
A
Hello,
GitHub
Universe,
my
name
is
Cassidy
Williams
and
I'm.
The
CTO
at
contenda
and
I
am
so
excited
to
talk
to
you
today
about
team
knowledge
sharing.
So
what
if
someone
on
your
team
suddenly
won
the
lottery?
What
if
they
won
the
lottery
signed
out
of
the
team
chat,
and
you
never
heard
from
them
again
well,
first
of
all
good
for
them,
I'm
happy
for
them,
but
would
your
team
be
in
trouble?
Would
all
of
their
knowledge
go
out
the
door
as
they
sailed
off
into
the
sunset
on
a
really
nice
boat?
A
Let's
talk
about
team
knowledge
as
your
teams
grow.
So
does
the
collective
knowledge
that
you
built
together,
it
can
be
challenging
to
manage
all
of
that
knowledge
and
document
it
all
and
create
new
ideas
without
Reinventing
the
wheel
and
bringing
your
team
members
into
your
space
to
add
even
more
knowledge
to
that
pile
writing
down
ideas
that
you
want
to
propose,
meeting,
minutes
or
even
notes
about
conversations
with
teammates
is
important
for
remembering
what
happens
throughout
your
day.
A
It's
a
way
of
not
only
just
committing
pen
to
paper
or
text
to
screen,
but
also
committing
attention
to
the
topic
that
you're
jotting
down
countless
studies,
I'm
not
going
to
talk
about
all
of
them
here.
Countless
Studies
have
shown
that
some
physical
process
needs
to
be
completed
to
form
a
memory
which
focuses
our
attention
in
our
brain.
To
remember
something
better
when
you
want
to
remember
something,
you
want
to
write
it
down,
ideas
and
Creative
Concepts
snowball
they
grow.
A
A
Now
imagine
if
your
team
developed
writing
things
down
as
a
habit
together,
not
just
you
think
of
the
ideas
that
you
can
come
up
with
and
iterate
on
that
as
a
group
by
just
keeping
a
record
of
the
work
that
you've
already
done,
you
could
do
a
lot.
This
is
the
kind
of
creative
work.
That's
what
we
need
to
push
for
as
developers,
it's
easy
to
get
bogged
down
with
processes
and
meetings
and
bike
shedding.
A
But
if
you
collectively
work
together
to
catalog
and
ideate
amazing
features
and
products
and
even
bug
fixes
awesome
things
could
happen
now
on
the
other
side
of
the
note-taking
coin.
Searching
amongst
your
team
notes
and
documentation
can
be
a
challenge
they
tend
to
pile
up
over
time.
Knowledge
sharing
without
structure
is
very
rarely
helpful.
A
It's
hard
to
remember
exactly
what
you
were
thinking
or
the
exact
words
or
phrases
that
you
were
using
when
you
originally
jotted
down
the
ideas
who
originally
said
those
ideas,
we
just
lose
that
essential
context
way
too
quickly
as
humans
who
have
lives
outside
of
work
and
tasks
to
do
throughout
the
day
and
just
a
lot
of
things
on
our
minds.
That
being
said,
thinking
too
much
about
making
your
team
notes
searchable
can
bog
you
down
as
you're
writing
them.
If
you
have
a
gigantic
template
where
you're
like.
A
Oh,
we
need
to
fill
out
every
single
thing
before
we
can
write
down
ideas.
This
isn't
productive
ideas
are
fleeting
and
they
can
be
very,
very
powerful
over
time
if
they're
captured
well,
but
once
again,
if
you're,
focusing
too
much
on
how
you'll
organize
them
as
you're
writing
them
down
every
single
time,
you'll
lose
what
you
want
to
capture
slowly,
but
surely
the
key
is
to
have
a
predictable
system
for
your
notes.
There's
a
helpful
principle
from
the
book:
how
to
take
smart
notes
by
sonke.
A
Aarons
standardization
enables
creativity,
you
don't
want
to
spend
unnecessary
energy
just
trying
to
find
the
knowledge
you
need
as
you're
brainstorming
with
your
team
and
applying
decisions.
You
want
to
have
an
easy
to
navigate
predictable
system
for
your
notes
when
you
have
common
formatting,
an
organization
and
a
shared
understanding
of
how
to
document
things
and
quickly,
your
team
can
think
and
reflect
and
hypothesize
and
discuss
test
share
more
together
and
that's
the
creative
work
that
really
matters
there
isn't
any
silver
bullet
system
for
your
notes,
there's
no
one
tool
that
will
work.
A
One
thing
that
will
make
everything
work
for
you.
The
way
your
team
decides
to
take
notes
is
up
to
your
team.
On
one
of
my
previous
teams,
I
worked
on,
we
loved
having
brainstorming
sessions.
Together,
we
would
do
mob
programming.
We
would
come
up
with
cool
ideas.
We
would
regularly
get
on
calls
and
hash
out
a
concept
that
we
thought
might
be
interesting.
We
would
think
about
big
ideas
for
new
projects
that
we
could
build
together.
A
We
would
even
just
talk
about
different
solutions
for
problems
that
were
on
our
doorstep
and
upcoming
deadlines,
but
occasionally,
as
we
wrote
down
what
happened
in
those
meetings,
we
ran
into
issues
with
consistency,
because
we
wouldn't
always
write
down
what
happened
and
not
everyone
had
the
same
takeaways.
We
also
ran
into
issues
with
not
knowing
who
was
taking
notes,
because
the
same
people
would
always
take
them
and
if
they
were
out
the
notes
just
wouldn't
be
taken,
and
we
had
issues
with
finding
old
notes
when
an
idea
was
on
the
tip
of
our
tongues.
A
But
we
didn't
know
where
to
find
them
for
us.
Developing
our
own
system
for
taking
care
of
notes
was
really
important
for
throwaway
notes.
We
made
a
scratch
Pad
section
of
our
notion
where
we
would
jot
things
down
that
weren't
fully
fleshed
out
where
we
could
just
kind
of
put
things
on
paper
quickly
and
then
pick
it
back
up
later.
A
We
also
developed
templates
for
ourselves
where,
for
each
type
of
meeting,
they
were
all
linked
back
in
a
directory
of
sorts,
with
a
table
that
allowed
us
to
search
by
date
by
type
the
people
involved,
and
we
also
made
a
rotation
for
who
would
take
notes
in
a
given
meeting.
It
was
clear
on
our
calendars
from
the
start,
who
we
could
hand
off
the
responsibilities
to
as
changes
arose.
This
system
worked
for
our
team
super
super.
Well,
our
expectations
were
set.
A
Our
output
was
more
clear
and
we
were
honestly
just
overall
happier
with
how
our
meetings
went,
because
we
had
more
clear
notes.
It
meant
that
we
could
manage
our
time
better
in
that
not
every
meeting
had
to
be
required
for
us
to
get
the
full
context
of
what
we
needed
to
know.
This
system
may
not
work
for
your
team
once
again.
The
way
your
team
decides
to
take
notes
is
up
to
your
your
team.
A
In
the
end,
as
long
as
there's
a
shared
buy-in
in
which
everyone
uses
the
same
approach,
that
is
ultimately
what
matters
my
biggest
learning
around
notes
in
general
with
my
previous
team
system,
and
my
own
notes
is
that
they're
not
etched
into
stone.
You
shouldn't
treat
notes
as
if
they're
permanent
precious
pieces
of
information
notes
can
be
composed
together,
they
can
be
moved
around,
they
can
be
changed.
They
can
be
evolved
over
time.
Just
like
the
code
that
you
write,
you
can
build
off
of
them
and
iterate
to
make
your
ideas
better.
A
This
is
something
that,
once
again,
I
do
with
my
own
notes:
I
love
the
concepts
of
linking
your
thinking
and
second
brains
as
a
place
to
write
and
move
and
grow.
My
own
personal
notes,
I
use
a
software
called
obsidian
for
this
there's
countless
others
like
Rome
and
bear
and
notion
Etc.
That
lets
me
backlink
between
notes
and
create
a
sort
of
Wiki
for
myself
as
I
write.
A
Because
of
my
notes,
all
that
being
said,
write
things
down
and
don't
overthink.
You
can
always
go
back
later
with
refinements
and
new
ideas,
and
even
grammar
changes.
Don't
overthink
it
just
write
things
down.
There
is
a
system
called
the
para
method
by
the
Forte
Labs
organization
that
might
be
useful
for
your
team.
It's
broken
down
into
four
sections.
First
of
all,
there's
projects
where
project
notes
are
tasks
linked
to
a
goal
with
a
deadline.
These
could
be
app
mock-ups
product
specifications
or
a
blog
posts.
A
For
example,
the
a
is
area
of
responsibility,
which
is
a
sphere
of
activity
with
a
standard
to
be
maintained
over
time.
This
could
include
professional
development,
direct
reports,
products
and
just
writing
blog
posts
or
something
the
r
is
for
resource
a
topic
or
theme
of
ongoing
interest.
This
could
be
project
management,
linting
notes,
teammate
information
and
then
that
last
day,
archives,
which
is
inactive
items
from
the
other
categories,
so
projects
that
are
completed
or
are
inactive
areas
that
you're
not
as
committed
to
anymore
resources.
A
You're
no
longer
interested
in
you
don't
have
to
follow
these
rules
perfectly.
This
is
just
an
example
system,
but
it's
a
good
initial
set
of
guidelines
that
can
be
helpful
for
your
team,
as
you
establish
your
own
best
practices
for
yourselves,
enabling
your
team's
strengths
and
how
they
organize
and
understand.
Information
is
particularly
helpful
as
you
establish
a
knowledge
base
for
yourselves.
The
software
you
use
does
not
matter
for
this
system.
This
could
work
in
Evernote.
It
could
work
in
Dropbox.
It
could
even
work
in
a
GitHub
repo.
A
It's
about
the
way
that
you
use
it
and
once
again
having
a
shared
buy-in
from
everyone.
So
what
about
that
lottery
winner?
You
know
it
might
not
be
a
lottery
winner.
It
might
be
something
way,
less
exciting
that
pulls
your
teammates
away.
If
and
when
that
happens,
and
it
inevitably
will,
when
someone
decides
to
switch
jobs,
when
someone
wants
to
work
on
something
new
or
even
if
someone
needs
to
go
on
a
well-deserved
vacation,
would
your
team
be
able
to
manage?
Would
anything
be
in
Jeopardy?
Would
your
project
be
at
risk?
A
The
risk
of
not
writing
things
down
in
a
searchable
way
means
that
the
knowledge
with
that
person
could
go
away
and
it
happens
all
the
time
establishing
a
culture
of
documentation
where
your
team
has
a
shared
system
of
both.
How
and
where
they
should
write
can
help
with
this.
Now
you
don't
want
to
become
data
hoarders.
A
Necessarily
it's
a
very
good
thing
to
regularly
audit
your
notes
and
your
documents
as
being
out
of
date
or
archivable,
but
having
the
context
available
to
anyone
who
might
need
it
will
pay
dividends
over
time
moving
forward
in
general,
it's
very
easy
to
under
document
everything
because
there's
simply
too
much
to
know
and
things
change
too
often
or
over
document
everything,
and
then
every
single
page
turns
into
a
deep
Rabbit
Hole
of
connecting
information.
Finding
that
balance
is
important.