►
From YouTube: 2023-08-08 WG Platforms Project Meeting
Description
TAG web site: https://tag-app-delivery.cncf.io/
TAG Slack channel: https://cloud-native.slack.com/archives/CL3SL0CP5
TAG git repo: https://github.com/cncf/tag-app-delivery
TAG meeting notes: https://docs.google.com/document/d/1OykvqvhSG4AxEdmDMXilrupsX2n1qCSJUWwTc3I7AOs/edit
A
C
B
B
Nice
day,
yeah
pretty
good
I'm
doing
a
rename
of
something
which
requires
like
parsing,
actually
because
it's
like
a
I'm
looking
for
the
word
cluster
in
a
repo
that
talks
about
kubernetes.
So
it's
it's
been
fun.
D
Hello,
hello,
I'm
everything,
I'm
everything
all
right.
Yes,
so
you
know
it's
been
a
long
day.
A
B
I
can
give
it
a
go
to
start.
I
may
need
to
pop
off
a
few
minutes
early
depending
on
where
we're
at
in
topics
and
things.
So
we
can.
You
can
pick
up
from
where
I
leave
off.
If
that
happens,
or
else
I'll
try
and
stick
it
out
for
the
whole
the
whole
hour.
So.
B
Amazing,
thank
you
very
much
so
per
usual,
we'll
we'll
go
based
on
the
the
note
stock.
So
come
join
us
if
you're
not
there
already.
If
there's
something
you
want
to
talk
about,
that's
not
on
there
go
ahead
and
add
it
to
the
agenda
and
we'll
we'll
make
sure
to
cover
it,
give
it
another
minute
or
two
for
people
to
come
by,
but
we
are
nearly
there.
E
Part
of
it
and
I
would
like
to
if,
if
time
permits,
I
would
like
to
introduce
myself
who
I
am
when,
when
is
the
right
time,
I'll
be
happy
to
do
that,
and
let
me
know
that's.
B
B
Second,
it
comes
from
a
couple
of
other
conferences
that
do
that,
but
sort
of
just
a
short
intro
would
be
amazing,
and
then
often
people
have
more
things
they
want
to
share,
and
then
we
can
always
schedule
in
you
know
time,
for
you
know
product,
deep,
Dives
or
story
deep
Dives
based
on
on
the
intros
So
yeah.
Thank
you.
Dj
definitely
want
to
hear
from
you
so
we'll
just
give
it
I.
Usually
wait
till
I
think
we
usually
wait
till
about
the
five
minutes
pass.
B
Just
because
meetings
try
and
give
people
a
chance
to
show
up
and
then
we'll
then
we'll
kick
off.
B
All
right,
that's
the
tick
over
so
yeah
DJ.
If
you
don't
mind,
kicking
us
off.
Tell
us
a
bit
about
yourself
and
welcome
to
the
group.
E
Thank
you
and
the
easiest
way
for
me
to
introduce
in
90
seconds
that
you
gave
me
is
through
slaves,
which
I
always
kind
of
not
fonder,
but
I
want
to
make
sure
that
I
am
prepared
whenever
it's
needed
so
and
I'm
Vijay
and
then
I
have
education.
E
I
have
dual
Masters,
along
with
a
and
ml
certifications
and
in
different,
both
in
computer
science,
as
well
as
in
MBA
and
HR,
and
have
been
working
in
the
industry
for
15
years
in
various
companies
like
Oracle
and
open
text,
and
also
and
DST
for
the
first
seven
years
of
my
career
and
then
second
second
half
mostly
into
Comcast
and
into
various
departments
within
the
company,
starting
as
a
performance
consultant
and
building
high-scale
data
streaming
platforms
and
then
moved
to
machine
learning.
E
Department
in
the
customer
experience
division
of
it
and
we
built
them
platforms
there
and
then
now
I
moved
to
engineering.
My
internship
role
in
the
A
and
Discovery
organization,
building
the
next-gen
platforms
and
at
Conquest
and
at
work
like
yeah
technically,
like
I,
was
hands
on
into
performances
during
my
entire
career
from
The
Internship.
Until
until
now,
even
now,
I
see
as
a
performance
is
my
core
strength,
and
this
look
at
systems
at
scale
have
been
also
a
lot
of
participating.
E
A
lot
of
ergs
and
also
I
technically
involved
in
a
lot
of
initiatives
across
the
company
outside
and
within,
and
impact
wise
I
I
do
as
I
also
do
as
a
guest
faculty,
and
also
mentoring.
Some
students
from
the
non-profit
organizations
and
I
go
for
campus
setting
in
various
universities
so
far
and
and
I
believe
in
scalable
technology
and
its
impact
on
humanity
is
a
big
thing.
E
That's
where
like
why
I
try
to
Technologies
because
of
that
and
education
for
all,
is
what
the
cars
that
I
believe
in
and
then
the
journey
I
am
progressing
and
where
I
am
heading
and
what
I
am
enjoying
right
now
is
executive
and
the
strategy
and
Leadership
side
and
mentoring,
and
coaching
and
education
for
all
and
authoring
Technical
books
and
Leadership
side
is
that
I
am
heading
to,
and
areas
of
focus
is
fine,
and
then
technical
landscape
is
typically
like
is
what
most
of
the
data
streaming
platforms,
as
well
as
the
a
service
mesh
micro
services
and
also
solving
systems
at
scale.
B
That's
awesome,
thank
you.
So
much
I
feel
like
whenever
someone
asks
me
who
I
am
I
Stumble
through
it
for
about
30
to
60
seconds.
That
was
that
was
extremely
informative
and
very
well
aligned
with
what
we.
What
we're
up
to
here.
So
the
one
thing
I
guess
I
didn't
gather
from
that
was
was
how
you
found
us
like.
How
did
you
decide
to
come
to
the
meeting
today?.
E
Yeah
yeah:
that's
a
long
story
like
I
I'm.
In
definitely
I
myself
used
to
feel
like
platform.
Engineering
is
my
in
My
DNA
from
last
seven
years,
because
I
wanted
to
apply
in
Google
is
only
a
fan.
Companies
have
that
role
whenever
I
apply,
I
got
some
setbacks
and
when
I
was
always
seeing.
E
This
is
a
big
thing
in
the
industry
why
people
are
not
noticing
it,
but
now,
when
I
see
this
this
becoming
a
thing
and
I
think
I
myself
said:
okay,
let's
see
what
is
going
on
in
the
industry
and
I
I'll
I
use
a
lot
of
cloud
native
computer
Foundation
tools
and
Technologies
already
so
I
use
that
as
in
landscape,
is
my
go-to
place
for
anything
that
I
do
first.
So
when
I
see
this
working
group
on
the
platform
say
defining
this
as
a
model
that
virtuality
model.
E
B
That's
awesome,
yeah,
it's
just
it's
good
to
hear
sort
of
what
what
makes
the
group
visible
to
people,
because
that's
one
of
the
things
we've
been
talking
about
is
how
to
to
make
it
more
approachable
and.
B
E
E
We
we
used
to
work
here
like
almost
seven
years
before
in
my
these
two
presidents,
tooling,
and
when
I
see
his
talks
and
are
like
and
then
that
I
was
looking
for
I'm
building
some
kind
of
a
maturity
model,
but
not
on
the
platform
side,
but
more
on
the
the
double
productivity
and
different
side
and
when
I
see
like
when,
when
I
see
his
talks
and
then
oh
I
think
what
is
this
maturity
model
I
went
through
that
from
the
on
the.
B
B
Thank
you.
I
think
Vijay
you're
you're
our
only
newcomer
today,
so
the
one
downside
of
the
newcomer
intros
is
you
don't
get
to
know
you
don't
get
the
the
huge
interest
to
the
rest
of
us
but
happy
to
answer
questions
about
you
know
where
we
come
from
and
all
that
as
we
go.
B
The
big
thing
that
we
are
going
to
cover,
as
we
always
do,
is
sort
of
updates
on
where
we
are
on
projects
and
and
he
asks
that
people
have
around
those
and
then
if
we
can
we'll
spend
a
little
bit
of
time
diving
into
one
of
the
projects,
if
it
makes
sense
with
the
group
that
we
have
and
the
time
that
we
have,
but
that's
sort
of
the
like
extra
benefit
if
possible.
B
So
we
I
don't
see
Leanne
here
and
I'm,
not
sure
if
anyone
else
has
context,
but
there's
been
work
around
the
restructuring
of
the
the
tag
website,
which
I
know
has
also
been
a
topic
of
conversation
at
the
tag
meetings.
B
I
think
that
they're
was
a
issue
where
the
pr
had
a
bit
of
so
there's
sort
of
two
two
two
topics
on
this:
the
top
two
items.
So
we
have
both
a
restructuring
of
the
website
which
I,
don't
think
yet
has
been
merged
again
it
was
merged
once
but
had
failures.
B
B
Once
that's
done,
we
so
that's
the
second
bullet
point,
but
the
top
bullet
point
is
actually
what
will
be
unlocked,
which
is
that
there's
been
a
lot
of
great
work
around
a
prototype
for
creating
a
platform,
and
we
want
that
to
live
on
on
the
website
and
be
something
that
people
can
make
pull
requests
into
as
examples
and
and
make
that
visible.
So
I
don't
have
a
lot
of
context
on
that.
I,
don't
see
the
end
here.
D
I
haven't
been
able
to
get
to
the
tag
meetings,
so
I
haven't
I,
just
know,
there's
stuff
going
on
with
the
website.
Yeah.
B
I
think
we've
got
to
figure
out
people
with
merge,
merge
abilities,
testing,
emerging
abilities
of
that
website,
so
that
we
can.
We
can
help
get
that
across
so
I'll,
maybe
try
and
reach
out
to
Josh
and
just
see
what's
on
his
radar
and
who's
who's.
Looking
into
that,
but.
B
So
I
I
think
that
the
only
context
I
have
is
that
it
was
merged
once
it
had
some
some
like
linking
issues.
So
there
are
some
dead
links
unintentionally
and
then
so
it
got
reverted
and
then
I
don't
know
what
work
has
been
done
since
the
revert
to
to
revalidate
so
I,
wouldn't
I
wouldn't
hit
the
merge
button
right
away
without
without
checking
that
stuff,
but
yeah,
that's
sort
of
where
we're
at
so.
B
If
anyone's
interested
in
website
stuff
Leanne
has
been
taking
a
lead
on
that,
but
I'm
sure
it
would
be
open
to
more
collaborators
so
reach
out.
If
you're
interested
in
that.
C
For
the
prototypes
part,
so
it
sounds
like
we're
still
trying
to
make
a
decision
about
what
we
want
to
do
with
that.
It
sounds
like
it's
still
kind
of
like
a
bit
more
ambiguous
is
that
is
that
correct.
B
Without
you
know,
progress
over
Perfection
kind
of
idea,
I
think
the
idea
was
to
take
a
few
of
the
existing
prototypes
and
figure
out
how
to
package
them
and
make
them
available,
as
you
know,
not
sanctioned
use
this
in
production
kind
of
ideas,
but
as
like
what
they
are,
which
is
examples
that
achieve
certain
like
behaviors
or
certain
outcomes
and
then
from
there
try
and
describe
what
would
be
a
more
holistic
view
of
these
prototypes
and
and
why
prototypes
might
be
listed
there.
B
So
so,
basically,
try
and
surface
the
prototypes
before
we
worry
too
much
about
like
the
organization
organizational
structure
around
it.
That
was
my
last
understanding.
From
from
the
last
tag,
the
one
last
working
group
meetings.
C
So
what
practically
I
know
that
they've
got
that
we've
got
that
PR
last
time.
It
was
two
weeks
ago
so
I'm
just
trying
to
figure
out
like
practically
what
what
does
it
look
like
for
us
to
start
to
kind
of
move
forward
on
trying
to
surface
some
of
that.
B
I,
don't
know
so
I
think
we're
gonna
have
to
Ping
Leanne
in
in
slack,
probably
and
try
and
get
an
update,
an
async
update.
Unfortunately,
so
yeah.
C
B
B
Cool,
if
there's
nothing
else
on
those
two,
mostly
because
it's
a
lot
of
questions
without
a
lot
of
answers
today.
Sorry,
the
next
one
on
the
list
is
the
maturity
model.
So
this
one
has
been
picking
up
steam,
which
is
awesome.
We
are
in
a
state
where
we
have
done
two
deep
Dives
sessions
in
a
synchronous,
kind
of
call
format.
B
Okay,
so
I
think
what
you
can
see
now
is
our
platform
working
notes.
This
is
what
we're
working
off
of
here
today
and
we're
sorry
about
that.
I
should
have
showed
it
sooner
and
so
we're
now
at
the
platform
maturity
model
and
where
we've
gotten
to
is
we
sort
of
parked
the
big
document,
because
we've
talked
about
how
there's
like
sort
of
three
sections
to
that
document?
There's
like
the
preamble.
B
Why
is
this
document
exist?
How
do
we
expect
people
to
use
it
then
there's
the
table
which
is
sort
of
the
screenshotable
slide,
deckable
high
level
overview,
and
then
there's
going
to
be
a
detailed
section
and
those
are
quite
tightly
coupled.
So
if
the
table
changes,
the
detail
section
has
to
change.
B
Obviously,
and
so
we
were
trying
to
focus
in
on
getting
the
the
model
the
table
section
more
stable
before
we
started
writing
investing
a
lot
of
time
in
the
details
section,
so
we
have
a
session
booked
for
tomorrow,
where
we
will
hopefully
review
this
table
and
and
decide
if
we
feel
like
it's
stable
enough
for
us
to
invest
in
in
the
more
detailed
write-ups
about
the
table.
B
I
think
some
things
to
call
out
if
you
haven't
seen
this
document,
yet
it
is
based
on
the
outcomes
of
the
the
previous
calls,
as
well
as
asynchronous
chatter,
in
the
slack
channels,
and
things
like
that,
I
tried
to
surface
some
of
the
shared
beliefs
that
that
came
out
so
that
we
we
would
be
on
the
same
page
and
so
that
people
could
could
challenge
any
of
these
assumptions
or
any
of
these
ideas
like
which
are
kind
of
underpinning
the
table.
B
So,
rather
than
kind
of
seeing
weird
things
pop
up
in
the
table
that
are
actually
challenging,
the
like
underpinnings
of
the
table,
I
tried
to
surface
those,
so
please
feel
free
to
like
question
and
ask
questions
and
challenge
any
of
these
and
then
separately
or
in
addition,
this
table
is
the
proposed
table
at
this
stage.
This
column
here
is
going
to
be
deleted.
B
Once
we
do
the
detailed
section
so
I
felt
like
it
would
be
hard
for
people
to
review
a
table
with
like
25
words
on
it
and
no
context
as
to
where
those
words
came
from
so
I
tried
to
give
like
a
sentence
or
two
of
context,
but
like
it's.
B
This
is
only
the
tip
of
the
iceberg
and
there's
going
to
be
a
much
more
kind
of
well-written
and
detailed
explanation
of
these
of
these
aspects
like
these
rows,
as
well
as
each
item
within
each
level
within
the
row
before
we
finish
so
don't
don't
stress
too
much
on
that,
but
yeah
so
I
think
things
to
call
out
is
that
these
are
there's
a
few
less
there's
only
five
things
listed
here,
whereas
I
think
in
the
past
we've
had
as
many
as
seven
or
eight
even
listed
at
one
point
so
something
to
to
think
about
if
we're
missing
anything
any
gaps.
B
The
other
thing
to
kind
of
keep
an
eye
on
is
I
would
say:
measurement
is
a
a
brand
new
Dark
Horse.
So
that
came
in
through
some
slack
chat
in
the
last
week,
and
so
does
that
fit.
Is
that
something
we
want
to
see
on
the
table
or
not?
And
if
so
are
these
levels
reasonable,
they're
sort
of
as
they
say,
not
something
that
people
have
reviewed
a
lot
of
yet
so
yeah?
So
we're
gonna
have
a
deep
dive
on
this
tomorrow
and
honestly,
looking
at
our
schedule.
B
The
last
item
that
we
want
to
talk
about
is
going
to
be
quite
similar
to
the
first
two
where
without
Michael
here,
it's
not
going
to
make
a
lot
of
sense
for
us
to
to
tackle
it
Michael's
introducing
another
piece
of
work.
He
wants
to
kick
off
with
the
group
around
I
guess
the
way
I
describe
it
is.
B
We've
talked
about
how
the
the
white
paper
is
like
kind
of
the
top
of
our
hierarchy
of
content
and
the
maturity
model
is
a
level
below
that
in
tangibility
and
and
kind
of
grounding.
But
it's
sure
as
heck,
not
a
you
know,
prototype,
which
is
another.
You
know
that's
levels
below
the
the
maturity
model.
We're
not
gonna,
be
talking
about
technology
in
the
maturity
model,
that
kind
of
thing,
but
between
maturity,
model
level
of
depth
and
something
like
a
prototype.
B
There
is
a
deep
dive
on
the
concepts
behind
the
maturity
model
that
you
know
we
we
won't
be
able
to
cover
in
a
consumable
maturity
model
and
so
he's
looking
to
put
together
something
that's
a
deep
dive
on
platform
as
a
product
as
a
concept.
I
think
there's
been
talk
now
recently
about
observability
or
measuring
of
your
platform
as
a
another
possible
example
of
like
a
detailed
paper,
we
can
write
that
would
kind
of
speak
to
if
you're
trying
to
achieve
maturity
on
this
model.
B
Here
are
you
know
more
tangible
things
you
can
look
at
and
how
those
work.
So
that's
the
context
of
the
piece
of
work
he
wants
to
do
it's
going
to
be
steeped
in
user
research,
around
end
user
platform,
engineering
teams
and
things
like
that,
but
so
there's
a
lot
of
work
to
be
done
there
around
how
we
get
those
interviews
with
end
users,
how
we
derive
data
from
the
then
and
therefore
influence
our
outputs
and
the
like
kind
of
structure
and
writing
of
that
paper.
B
But
I
know
he
has
a
bit
of
a
straw
man,
so
yeah
I,
don't
I,
don't
want
to
go
any
further
before
he's
able
to
introduce
it
that
I
just
want
to
give
a
bit
of
context
in
case.
That's
something
people
are
excited
about
because
come
back
it
will.
It
will
come
up
soon.
So.
C
Good
question
yeah,
specifically
on
the
deep
dive
for
tomorrow.
What
I
put
down
was
that
it
seems
like
a
bit
of
the
Deep
dive
is
going
to
be
fleshing
out
more
of
the
specifics
of
the
table.
So
now
that
we've
kind
of
got
the
general
structure
kind
of
diving
into
the
implications
of
that
and
what
that
would
kind
of
like
practically
look
like
to
I'm
gonna
put
pen
paper
and
build
that
out.
More
is
that
kind
of.
B
I
think
yeah
I
think
that
the
my
my
so
we
have
a
provisional
timeline.
We
we
are
not
deadline,
driven
just
to
be
clear,
but
keeping
in
mind
if
we
would
like
to
try
and
prepare
this
in
time
for
kubecon
Chicago
like
that
is
a
opportunity.
B
It
is
not
a
deadline
just
to
like
clarify
our
our
stance
on
this,
but
that
opportunity
we
would
probably
need
to
look
at
preparing
this
for,
like
kind
of
formal,
the
entire
paper
for
kind
of
formal
GitHub
review
the
way
that
we
did
with
the
the
white
paper
by
sort
of
middle
of
September,
which
would
give
us
about
a
month
of
that
formal
GitHub
review
before
we
would
be
able
to
then
have
about
a
month
of
like
publishing
and
paperworking
and
all
of
that
for
for
it.
B
So
with
that
in
mind,
the
thing
that
would
trigger
me
to
say,
hey,
that's
not
a
realistic
goal
would
be
if
we
leave
tomorrow
without
alignment
that
this
is
a
a
reasonably
stable
table.
So
my
goal
is
to
get
to
the
point
where,
whatever
the
table
state
is
at
the
end
of
tomorrow
is
reasonably
stable
would
be
my
goal.
Obviously,
if
people
feel
like
there's
a
lot
of
things
left
to
do,
then
there's
a
lot
of
things
left
to
do
and
we'll
we'll
tackle
those
and
then
the
second
goal
of
tomorrow.
B
If
we
get
there
is,
if
there's
people
who
want
to
take
ownership
over
writing
the
detailed
sections
for
any
portion
of
the
table,
we
need
to
get
kind
of
initial
Straw
Men
ideas
down
for
these
and
there's
going
to
be
a
lot
of
like
melding
of
of
writing
styles
and
things
to
be
done.
But
if
we
can
at
least
get
sort
of
ideas
of
what
people
want
to
be
highlighted
in
the
detailed
sections,
then
that
would
would
go
a
long
way
for
getting
us
started
on
that.
B
So
if
anyone
wants
to
own,
you
know
one
of
these
rows
or
if
people
want
to
own
a
column
or
whatever
I
think
that
would
be
cool
so
that
there's
more
diversity
in
those
voices
so
cool.
Thank
you.
No
worries
any
other
questions
about
either
the
meeting
tomorrow
or
anything
else
or
any
other
actions,
because
what
I'm
thinking
is,
if
we
don't
have
it
like.
B
D
I
really
want
to
be
mature.
It's
it's
about
time.
B
Adulting
is
hard
Robert,
I,
I,
don't
know
if
I
want
that
in
my
life,
but
okay,
all
right.
Well,
then,
you
know
if
anything
comes
up,
give
a
shout
but
otherwise
we'll
turn
our
attention
and
I
would
say.
B
F
F
Like
this,
this
is
awesome,
I
hadn't,
gotten
to
looking
at
the
new
table
that
y'all
made,
but
yeah
kind
of
gonna
glance
through
it
after
this
we're
gonna
review
it
carefully
after
this,
but
just
from
glancing
through
it
now
I
think
this
has
made
like
huge
strides,
so
really
great
work.
B
Yeah
I
think
one
thing
I'd
call
out
is
I'll,
actually
I,
don't
think
I
add
it
here.
Oh
I
am
not
hold
on
I'll.
Add
it
when
I'm
logged
in
so
give
me
a
second
also.
D
B
D
This
is
just
like
an
overview
over
the
you
know,
so
don't
don't
get
stuck
in
semantics.
A
D
A
I
would
say
so:
yeah
you're.
B
B
So
you
can
start
to
get
ideas
from
him
of
like
what
design
could
look
like,
but
that's
part
of
why
getting
ourselves
to
sort
of
content
complete
by
September
and
allowing
ourselves
time
to
have
that
content,
review
and
start
thinking
about
design
options
is
like
gives
us
some
time
to
do
that.
So
yeah
ain't,
no
designer,
but
the
the
for
context.
B
The
link
I
just
added,
is
what
we
did
at
the
last
Deep
dive,
which
is
that
we
basically
open
the
floor
for
anyone
to
sort
of
think
blue
sky
like
empty
page
about
this
model,
which
I
think
is
a
really
powerful
option,
depending
on
how
you
like
to
think
and
how
you
like
to
work
and
also
is
a
really
powerful
option,
because
I
think
it's
it's
very
hard
when
you
start
from
the
ground
up
to
try
and
divide
these
sections,
and
so
I
think
it
gives
a
little
bit
of
empathy
for
like
how
do
we?
B
How
do
we
design
these,
but
there's
some
really
good
ideas
that
are
what
drove
out
this
this
current
Table
so
feel
free
to
peruse
if
those
help
as
well
in
thinking
about
stuff
so.
B
Sure
so
this
is
the
the
doc
for
that
we're
currently
working
on
yeah.
B
E
I
have
one
question,
but
I
can
admit
because
I
I
go
through
this
table
in
detail
today
and
tomorrow.
I
can
come
up
with
points
if
there
isn't
valid
points
that,
but
so
one
of
the
challenges
with
adapting
Platforms
in
the
organizations
is
that
at
what
scale
of
the
other
organization
is,
and
if
it's
a
startup
to
Middle
the
the
and
also
the
moderate
scale
and
then
bigger
companies
right
and
depending
on
the
company
under
on
their
total
organizational
structure,
actually
also
influences
this
platform
maturity.
E
A
lot
I
have
worked
in
XP
I,
have
experience
in
all
of
these
companies
and
when
I
look
back
in
my
entire
carry
around
and
when
I
see
the
themes
the
challenge
becomes
more
common.
It
becomes
more
complex,
a
challenge
when
it
moves
to
an
larger
animations
with
lot
of
different
teams
in
it
right.
So
when
we
try
to
adopt
these
models
and
how
we
can
add
a
dimension
to
this
in
the
organizational
scale
that
gives
us
a
more
thought
provoking
table.
E
For
example,
if
I'm
an
executive
director
at
the
small
company
right
when
I
look
at
the
stable,
it
doesn't
matter
to
me.
I'm
I'm,
not
they
give
these
people,
but
when
you
try
to
incorporate
that
also
into
this
kind
of
foundational
models,
no
one
will
neglect
these.
No
one
will
take
it
as
the
day.
It's
not
my
everyone
try
to
understand
it,
so
it
they
consider
this
also
as
a
dimension
from
small
to
medium
to
large
scale
Enterprises
and
they
Define
the
maturity
by
thoughtful
thinking
so
I'm.
B
Yeah,
let
me
see
if
I
can
reflect
back
if
I've
heard
correctly.
So
what
you're
saying
is
that
there
are
a
wide
range
of
kind
of
contexts
that
could
use
this
and
how
do
we?
How
do
we
validate
this
can
work
in
those
contexts?
I
think
that's
a
great
point.
I
actually
had
meant
to
bring
that
up.
That,
like
I,
think.
B
Another
thing
we
can
do
tomorrow
is
if
people
want
to
try
and
work
work
through
their
work
cases,
so
whether
they
be
former
jobs,
former
Consulting
gigs,
former
friends
of
theirs,
that
they
know
have
had
situations
like
I.
Think
talking
about
scenarios
associated
with
this,
and
could
you
could
you
use?
It
will
be
a
good
kind
of
litmus
test,
so
I'm,
seeing
some
nodding
I
think
that's
one
piece
of
the
thing
you
were
saying,
but
then
the
second
piece
of
the
thing
I
think
that
you're
saying
is
like.
B
E
First
point
is
correct,
and
second
point
is
also
that,
when
I
try
to
see
these
kind
of
maturity
models
and
try
to
adapt
as
an
organizational
leader
first
thing
I
look
at
is
that
did
they
consider
my
category
of
the
organization,
my
kind
of
scale,
my
kind
of
needs
and,
if
they
feel
oh
I,
think
this
report
is
mainly
for
this
maturity
model
is
meant
for
the
organizations
with
bigger
scope
and
bigger
teams
and
companies,
and
they
say
like
okay,
it's
not
belonged
to
me.
B
B
Right,
like
that's,
okay
and
so
I
think
where
we've
tried
to
tackle
that
right
now
is
in
the
kind
of
Preamble
in
that
introduction,
section
and
I
think
that
likely
could
use
a
refresh
once
we
sort
of
as
we've
kind
of
matured
our
own
thinking
about
the
model
as
we
go.
But
that's
one
location
where
I
know
that
we've
been
trying
to
a
add
that
Nuance
is
there
anywhere
else
that
you
think
we
could
add
that.
E
B
E
That's
why
I'm
missing
the
context
but
I
think
that's
a
perfect
place
to
be
in
perfect.
B
And
so
please
keep
an
eye
on
that
as
you
do
review
the
document,
because
it's
it
is
the
intention
to
have
covered
that
that
doesn't
mean
we
succeeded
yet
right.
This
is
all
still
in
review
and
so
you'll
see
like
that.
You'll
see
some
statements
in
here
that
hopefully
start
to
to
reference
that,
but
we
could
maybe
take
it
a
step
further.
Maybe
it
deserves
its
own
section.
I,
don't
know
like
that's
the
thing
that
we'll
we'll
start
looking
at
yeah
now.
So
definitely
awesome.
E
B
One's
offended
by
any
of
the
words
on
this
table,
I'm
very
I'm
I
you
either
are
so
offended.
You
can't
even
be
bothered
to
say
it
or
you've
fallen
asleep
and
you've
managed
to
still
look
like
your
eyes
are
open.
I
can't
I
can't
believe
that
we've
managed
to
get
to
a
table
that
people
are
not
offended
by.
It
would
be
a
miracle.
C
B
Yeah
and
that's
okay
and
we
can
pop
off
the
call
at
any
time,
there's
no
need
to
fill
the
hour.
I
just
wanted
to
give
space
in
case
people
weren't
going
to
be
able
to
make
it
tomorrow
if
they
wanted
to
or
if
they
felt
like.
We
were
in
some
sort
of
position
where,
if
we
were
to
come
in
tomorrow
to
the
call
we're
like
we're
in
a
trouble
Zone
that
if
we
could
tackle
something
today
before
that
call
tomorrow,
then
we
would
be
in
a
better
place.
B
E
Can
certainly
you
like
anyone,
but
mainly
that,
because,
as
a
first
time,
mentoring
into
this
space
and
I
feel
I
definitely
feel
it
belongs
to
in
this
community
and
I
want
to
see
like
how
I
can
find
the
possibilities
and
then
how
to
make
sure
that
I
involve
into
this
and
like
I,
need
few
minutes
of
guidance
on
that.
So
anyone
who
has
like
Ai
and
the
person
like
I
can
I
can
definitely
help
you
to
hand
holder
the
initial
phase.
So
I
would
like
to.
D
Oh
I
was
just
about
to
say
that
like,
but
probably
or
maybe
having
my
obstacle
but
I
I'll
at
least
stick.
Let
me
get
through
there.
Okay,.
E
So
one
of
the
one
of
the
challenge
that
I
see
in
the
platform
adoption
is
the
the
collab
communication
and
collaboration
within
the
organizations
and
which
section
of
these
is
covering
that
and
I
was
not
able
to
color,
especially
like
what
I
mean
to
say
is
that
when
I
try
to
build
a
product
internally,
like
especially
like
getting
a
buy-in
from
internal
teams,
you,
if
you
see
from
an
organization
within
the
organization,
that's
a
big
space
that
you
it
buying
in
by
other
teams,
is
so
hard
and
it's
almost
like
you
are
selling
your
product
to
a
person
that
who
don't
want
to
buy.
E
So
the
point
is
that
the
main
thing
that
links
is
that
communication
and
also
collaboration
aspect
of
it
and
then
the
platform,
engineering
teams,
the
maturity
comes
with
having
more
openness
in
the
communication
and
then
understanding
the
ideas
and
collaborating
each
other
right.
So
where
exactly
we
are
covering
in
this
particular
table,
I
I,
don't
know
if
it
belongs
to
or
not
also
but
I
I
personally
feel
me.
Building
the
platform
team
and
I
said
like
successful
team.
I
can
I
can
self
rate
it.
E
As
the
challenge,
what
I
facing
last
couple
of
years
is
that
influencing
everyone
to
get
it
adapted
and
then
maintaining
the
SLS
of
it
and
then
also
being
an
operationalization
of
it
and
then
making
sure
that
hey?
This
is
a
feature
coming
so
like
getting
the
requirements
from
them
to
recycle.
You
know
like
it.
It's
my
like
16
hours,
a
day
of
time
that
I
had
to
took
because
I
believe
in
this
model
and
I
took,
but
where,
in
the
table,
we
are
going
to
cover
that
kind
of
points.
D
I'm
not
sure
if
there's
any
one
point
where
that
is
covered
specifically
directly
but
I.
Think
it's
like
it's
it's
it's
a
mixture
of
some
of
these
categories.
I
think
that
kinda
answers
your
question
I
think.
There's
the
the
idea
about
how
to
get
adoption
of
the
platform.
It's
also
the
idea
of
how
to
get
investment.
The
investment
is
not.
You
know
not
necessarily
money
but
also
hours.
You
know
people
Etc
getting
people
to
understand
the
the
scope
of
what
you're
trying
to
do
and
get
back
in.
D
For
that
there's
also,
you
know
there's
other
aspects
here
where
that
kind
of
gets
touched
upon:
I,
don't
there's
like
I,
don't
necessarily
think
we
need
to
have
something
that
is
that
specific
to
those
specific
pain
points
but
I
think
they
get
covered
throughout
the
model
in
various
ways,
but
I
I.
Would
you
know
just
at
that
point
recommend
you
to
read
through
it
and
and
think
about
that
you
know
set
of
pain
points
and
try
to
see
if
you
can
find
it.
D
E
B
Amazing
yeah
I
think
that's
exactly
when
I
say
like
bring
challenges
in
this
in
the
sense
of
use
cases
tomorrow,
I
think
that's
exactly
what
you're
you're
doing
and
that's
exactly
what
you
know.
We
can
do
it
today
and
we
can
do
it
tomorrow,
but
that's
what
we
want
to
be
doing.
One
thing
I
heard
and
what
you
were
saying
is
that
you
have
applied
the
concept
of
platform
as
a
product
and
managed
like
managed
a
yeah.
B
You
basically
applied
the
platform
as
a
product
concept
or
Tech
technique
and
I
think
one
thing:
you'll
notice
in
the
evolution
of
the
table
from
this
initial
sort
of
stab,
which
has
been
a
bit
a
bit
extended
on
and
a
bit
hard
to
read
these
days.
But
you
can
see
it
started
with
something
like
platform
as
a
product
as
a
mature
level.
B
We've
moved
away
from
that
into
things
like
Community
enabled
and
product
budget
and
things
which
are
more,
which
are
trying
to
stay,
stay
away
from
techniques
and
tactics
and
and
more
look
at
like
drivers
and
outcomes
where
I
I'm
expecting
that
when
we
drop
into
the
detailed
section.
What
does
a
product
budget
mean?
B
Like
maybe
we'll
see
some
evolutions
of
it.
Maybe
we'll
see
some
like
improvements
like
clarifications
of
it,
but
I
would
say
that's
a
fair.
It's
hopefully
can
be
fairly
durable
and
what
I
think
what
you
might
see
in
sort
of
two
years?
An
update
to
this
thing
is
an
update
to
the
descriptions
which
is
like.
We
have
learned
that
to
create
that
optimized
platform,
the
techniques
that
we
were
advocating
for
today,
maybe
don't
stand
the
test
of
time,
as
well
as
the
concepts
that
we
put
into
the
model.
B
So
that's
sort
of
what
I
think
we're
we're
dry.
We're
attempting
to
do
is
create
that
durable
model
that
then
can
have
tactics
and
techniques
hung
off
of
it
and
that
those
can
evolve
with
with
time
and
with
learning
and
with
yeah
things.
So.
F
B
B
Thank
you
for
for
having
time
to
stay
on,
depending
on
where
that
chat
goes,
we
can
have
Josh
sort
of
just
cut
the
recording
or
we
can
turn
off
the
recording
now,
whatever
makes
sense
for
you,
YouTube
like
or
the
group
feel
free
to
do,
but
otherwise
I
look
forward
to
seeing
those
who
can
make
it
tomorrow.
So
yeah.