►
From YouTube: [2022-08-16] Next Architecture Workflow
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).
B
C
B
C
C
D
D
D
D
D
E
D
E
C
C
C
C
C
C
C
C
C
C
C
C
C
C
D
C
Marshall
cottrell
principal,
strategy
and
operations
(technical):
fork
of
groupon
going
right,
because
I
see
the
fork
of
groupon
turning
into
like
a
more
general
purpose
like
dashboard
solution,
and
that
seems
to
be
what
cube
dev
does
so,.
It
would
be
a
shame
if
we
end
up
with
two
like
distinct
dashboard
and
solutions
is
part
of
the
product.
C
C
C
C
Marshall
cottrell
principal,
strategy
and
operations
(technical):
and
on
to
number
four.
We
had
this,
mr
out
for
a
while.
I
I
resolved
a
couple
of
threads
with
to
do's
actions
for
me
to
go
back
and
fix.
I
saw
that
eric
had
some
feedback
shortly
after
I
merged
so
I'll
address
that
after
this
meeting.
C
E
E
Grzegorz
bizon
principal
engineer,
verify:.
What
I'm?
What
I'm
sometimes
missing
from
this
working
group,
is
a
clear
set
of
action
points
assigned
to
work.
Look
the
members
after
every
meeting,
so
that
I
could
actually
volunteer
to
do
a
bit
more
work
so
that
we
can
towards
the
exit
criteria.
Faster.
C
C
C
C
C
marshall
cottrell
principal,
strategy
and
operations,
(technical):
a
blueprint.
eric
johnson
cto:,
like
it
here
sorry,.
So
what
I
was
going
to
suggest,
as
I
got
that
I
think
a
template
is
the
way
to
make
an
like
an
artifact
deliverable
to
describe
what
something
is
and
then
it
gives
people
a
huge
head.
Start.
D
B
E
E
Grzegorz
bizon
principal
engineer,,
verify:
blueprints
written.
andrew
newdigate,
d.e.,
infrastructure:,
already
and.
grzegorz
bizon
principal
engineer,
verify:.
We
can,,
based
on
the
historical
evidence,
describe
what
do
you
usually
shouldn't
be
inside
a
blueprint,,
and
perhaps
this
description
somewhere
or
like
before
describing
a
template
could
also
help
people
to
actually.
D
eric
johnson
cto:
good
description
of
what
it
is
and
then
take
the
best
food
prints
from
the
past
and
look
for
the
common
elements
and
then
there's
be
one
of
the
template
and
then
it's,.
You
know
as
long
as
we're
flexible
about
the
template,
then
exactly
what
andrew
and
marshall
describe
sort
of
emerges.
C
Marshall
cottrell
principal,
strategy
and
operations,
(technical):
yeah,
and
I
think
that
spreadsheet
that
we
put
together
is
really
useful
because
it
links
you
to
both
the
blueprint
and
the
production
readiness
review
and
when
it
existed,
the
app
sec
review.
And
if
we
have
the
ambition
to
start
to
consolidate
some
of
those.
C
C
C
C
C
E
C
E
E
C
C
C
F
F
C
C
F
F
F
F
F
F
F
F
F
F
A
Chad
woolley
senior
engineer,
editor
(he/him):,
the
the
engineering
side
and
the
development
side
to
advocate
for
allocating
more
more
resources
to
maintenance,
work
or
technical
debt
or
whatever,,
and
I
think
what
eric
had
said
in
the
previous
meetings
is
that's
also
as
the
season,
a
framework
for
us
to
say.
Okay.
A
F
Fabian
zimmer
group
product
manager:,
I
think
that's
fair
enough.,
fabian
zimmer
group
product
manager:
like
this-
is
not
my
personal
take
on
it,,
but
to
take
it
as
a
personal
opinion,.
I
think,
having
more
data
is
valuable,,
but
as
in
being
able
to
say
across
the
organization
or
within
your
team,.
These
are
the
focuses,
and
I
think
that
can
help
us
make
better
decisions.
F
F
F
F
A
A
A
A
Chad,
woolley
senior
engineer,
editor
(he/him):;
no,
it's
it's!
It's
still
part
of
the
feature,,
especially
if
it's
not
if
it's
not
live
yet
right,
it's
all
still
in
development,
so
that
just
having
those
discussions
in
important
to
get
product
and
engineering
on
the
same
page,.
What
is
the
future?
What
is
not.
C
Chad
woolley
senior
engineer,
editor
(he/him):,
yeah.
marshall,
cottrell,
principal,
strategy
and
operations
(technical):.
I
think.
fabian
zimmer
group
product
manager:,
like.
marshall,
cottrell,
principal,
strategy
and
operations
(technical):
in
summary,
it
it.
marshall,
cottrell,
principal,
strategy
and
operations
(technical):.
It
seems
like
a
lot
of
the
mechanisms
that
I
thought
that
we
would.
C
E
E
E
C
C
C
C
Marshall
cottrell
principal,
strategy
and
operations
(technical):.
I
think
I
think
everything
that
we
put
in
an
opportunity.
Canvas
today
is
essentially
public
information,
there's
no
reason
to
hide
that,,
but
there
is
slightly
more
sensitive
information
in
the
form
of
like
investment
cases
and
stuff
like
when
it
comes
down.
To.
C
C
C
Marshall
cottrell
principal,
strategy
and
operations,
(technical):
it.
marshall,
cottrell,
principal,
strategy
and
operations.
(Technical):
product
produces
so
much
documentation,,
though,
like,.
How
do
you
distill,
like
a
bunch
of
user
studies
into
a
markdown
document?
Right?
I
don't
know
what
the
answer
is
there,,
but
I
think
there's.
C
F
F
F
F
Fabian
zimmer
group
product
manager:,
you
need
to
make
bigger
changes,
and
if
you
have
that
higher
level
sort
of
product
intend,,
you
have
to
answer
pretty
quickly.
It's
like
what
architecture
requirements
actually
follow
from
this,
and
I
think
that
is
maybe
something
where
we
we
struggled,
sometimes
because
it
can
really.
E
E
E
F
F
F
F
F
A
A
A
A
A
Chad
woolley
senior
engineer,
editor,
(he/him):
and
eric
is
you
know
our
conduit
to
the
highest
levels,
to
what
said
what,,
what
are
the
product
priorities,
and
how
does
that
affect
the
architectural
decisions
that
are
really
making,?
So
I
think
that
you
know
that
is
the
point
of
the
next
prioritization
group
to
help.
C
C
C
Marshall
cottrell
principal,
strategy
and
operations
(technical):,
you
know
here's
my
blueprint
product
manager,.
Please
write
an
investment
case
for
it,
so
that
I
can
get
it
prioritized
right
because
that's
no
different
from
a
product
manager
saying
here's
an
investment
case
engineer,.
Please
go
right.
The
architectural
blueprint
for
it,
right.
C
C
Marshall
cottrell
principal,
strategy
and
operations,
(technical):
they're,
trying
to
solve
right,.
So
I
think
I
think
it
should
very
much
be
a
process
that
works
for
everybody
and,,
like
the
validity
of
whether
we
continue
iterating
on
and
collaborating
on.
It
should
be
defined
by
like
what
it
is
not
like
who
created
it,
you
know.
C
E
E
E
F
F
E
C
F
Fabian
zimmer
group
product
manager:,
ask
you
know
folks,
it's
like
what
made
this
a
success,.
You
know
what,.
Why
do
you
think
this
worked
out,?
You
know
what
are
the
some
of
the
downsides
and
upsides
and
then
see
what
comes
back
because
I
think,.
Maybe
that
is
what
we
can
use
this
data
to
make
that
a
little
bit
more.
F
F
F
E
Grzegorz
bizon
principal
engineer,
verify:
in
case
of
architecture
motion
workflow.
That's
also
they're
all
of
architecture
of
ocean
coach,
so
because
this
person
not
only
can
help
with
describing
the
technical
direction,
but
should
already
have
some
connections
in
the
company
to
make
it
easier.
To.