►
From YouTube: 2022-12-13 Product Analytics Sync
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
Hello,
everyone
and
welcome
to
the
December
13th
yep,
that's
right
back,
analyticsync
hope
everyone's
doing
well.
Hopefully,
everyone
can
see
my
screen
awesome
cool,
then
we'll
go
ahead
and
get
started
with
the
Board
review.
We
have
a
couple
issues
here
that
we
have
are
still
on
open
for
pre-aggregation
to
session
analytics.
I,
just
don't
think
that's
been.
The
focus
Max
I
think
is
that
the
case.
B
No
no
I've
been
working
on
them,
there's
no
specific
sort
of
outcome
for
them,
it's
more
about
just
learning
how
they
work,
how
we're
going
to
use
them
and
they've
sort
of
spawned
a
few
open,
Mrs
first,
which
pre
aggregation
I've,
been
working
on
today,
making
sure
that
works.
There's
a
point
in
the
agenda
later
on
to
discuss
how
we
want
to
go
ahead
with
that
in
the
future.
But
short
version
is
pre.
Aggregation
works
and
makes
a
big
difference.
B
A
Awesome
should
we
go
ahead
and
move
these
into
in
development,
then
I
guess
has
it
in
progress
state
for
investigation
issues.
A
A
Cool,
adding
support
or
adding
a
button
to
go
back
to
the
tracking
view
from
the
dashboard
listing
is
unassigned
and
blocked.
So
we'll
just
keep
moving.
A
B
Yeah,
no,
no,
that's
part
of
the
propagation
yeah!
That's
what
I'm
looking
into
all.
A
D
Yeah
so
I'm
working
on
it,
hopefully
I'm
moving
to
review
today
or
tomorrow,
and
this
will
unblock
the
first
one
that
we
had
on
on
block
the
one
to
go
back
so
hopefully,
I
can
also
work
on
that
as
a
follow-up
that
one
yeah.
C
Yeah
apologies.
My
camera
doesn't
seem
to
want
to
work
today.
I'll
figure
that
out
after
this
meeting
waiting
for
the
stack
set
up
is
in
Dev
making
decent
progress.
I've
got
the
basic
UI
in
now,
I
just
need
to
add
the
functionality
to
trigger
the
graphql
endpoint.
So
it's
going.
Okay.
A
That
I
have
the
next
one
for
the
demo
test
k11
since.
D
A
Have
to
connect
to
the
excuse
me:
sandbox
cluster
have
not
made
progress
in
this
fund.
I've
been
focused
on
the
internal
handbook
and
then
also
the
production
change
request,
which
is
happening
actually
after
this
meeting
and
then
I
guess.
As
an
aside,
the
internal
handbook
Mrs
were
emerged
and
I
suppose
we'll
see
that
in
the
verification
section
or
it's
already
been
closed,
but
we
can
go
talk
about
that
later.
When
we
get
to
it,
then
we've
already
covered
Max's
issues.
A
So,
oh
yeah,
sorry,
it's
in
review
here,
tracking
the
needs,
a
new
tracker
on
the
additional
handbook.
That's
been
merged,
that's
already
collecting
data.
So
that's
good
I
have
noticed
some
weirdness
with
the
juicy
configurator
which
I'm
investigating
because
it
likes
to
just
forget
sources
and
destination
configurations.
I'm,
not
sure
why
which
can
cause
issues
with
oven
collections.
So
I'm
going
to
be
digging
into
that.
Hopefully
later
today,.
A
C
A
As
far
as
I
understand,
they
have
the
person
opening
that
discussion
hasn't
yet
responded,
but
they
have
also
pushed
the
changes
forward
in
a
separate
Mr.
So
as
far
as
our
concerned
in
terms
of
tracking
usage,
this
is
in
I
would
say
verification,
or
actually
we
probably
go
ahead
and
close
this,
because
I've
already
verified
that
we're
collecting
events.
A
Is
still
I'm
not
sure,
what's
happening
with
that
discussion,
to
be
honest,
but
I've
responded,
Eugene
McManus
also
responded,
so
any
other
follow-ups
with
that
discussion.
I'll
keep
the
goop
in
the
loop
but
yeah.
That's
all
I
know
at
this
point.
A
And
then,
actually,
after
this
meeting
I'm
meeting
with
John
Jarvis
to
get
the
production
chain
request,
hopefully
sorted
out,
and
hopefully
we
can
get
that
going
for
both
staging
and
production
and
yeah.
Hopefully
that
goes
smoothly.
A
Next
up
we
have
dashboard
list
of
dashboards,
but
Jan
is
unfortunately
not
available
right
now.
So
we
will
move
on
to
the
next
issue,
which
we
have.
C
Yeah,
so
this
has
already
gone
through
review
with
Axel.
Thank
you
very
much
for
your
brilliant
review.
Passed
on
to
maintainer.
Don't
expect
any
major
issues
should
be
merged
in
the
next
day
or
two.
D
A
Great
okay
and
then,
as
far
as
our
we
don't
have
a
bookmark
for
the
last
I
think
there
was
no
new
issues.
I
think
that
was
the
last
of
us.
So
we
had
the
line
chart
as
our
last
closed
issue.
So
then
we
can
take
a
look
at
what
we've
got
so
far.
We've
got
the
table
merged
in
the
single
stat
as
well.
You
know
it's
not
available,
but
actually
was
there
anything
you
wanted
to
mention
about
the
single
stat,
rendering
widget.
A
Awesome
and
then
we
have
create
the
the
Baseline
application
for
the
onboarding
app
Rob.
Anything
you
wanted
to
call
out
here.
C
A
Great
all
right
and
then
I
think
I've
already
mentioned
the
internal
handbook,
so
that's
live
and
running
and
collecting
data.
So
it's
good
to
see
the
progress
so
far.
F
Where
you're
you're,
seeing
the
data,
are
you
seeing
anything
interesting
or
a
lot
more
volume
than
we've
been
seeing
previously
or
what?
What
sort
of
things
are
you
noticing
in
the
data
coming
in.
A
I,
haven't
done
any
analysis
yet,
but
the
volume
isn't
perhaps
the
most
I
mean
I,
don't
think,
there's
been
like
a
significant
increase
in
volume,
I
would
say
part
and
the
like
I
guess
partially,
due
to
the
fact
that
most
everything
goes
to
the
external
handbook
by
default
and
then
anything,
that's
you
know
more
confidential
or
safer
or
such
go
into
the
internal
handbook,
but
yeah
I
haven't
seen
it
I
haven't
done
any
analysis
to
really
say,
like
anything
different
other
than
you
know,
we're
not
casting
a
wider
net
on
things.
A
That
said,
as
I
mentioned
before,
the
one
thing
I
did
notice,
which
doesn't
really
particularly
related
to
the
data
is
that
the
Jitsu
configurator?
It
can
sometimes
forget
where,
where
data
is
supposed
to
go
when
you're
sending
the
events
so
I
don't
know
if
people
have
seen
it,
but
sometimes
you'll
see
the
post
requests
fail.
A
So
that's
something
that
I
I
find
quite
concerning
that
I'm
going
to
be
taking
it
to
today
so
yeah,
but
as
soon
as
that
started
out,
then
I'll
definitely
be
looking
to
look
at
the
schemas
that
Max
put
together
and
start
playing
with
the
data
and
also
update
the
test
data
set
for
those
who
want
to
take
a
look
at
themselves.
E
A
Yeah,
so
my
my
main
priority
is
to
make
sure
that
the
events
actually
go
where
they're
supposed
to
when
that
happens,
then
because
the
clickhouse
server
is
doing
fine.
So
that's
not
the
issue,
but
anyways
I'll
keep
everyone
updated
on
that,
in
addition
to
that,
Sam
and
I
have
done
Milestone,
pre-planning
and
I.
Think
we've
established
some
good
things
for
for
the
upcoming
Milestone.
A
So
please
take
a
look
at
that
planning
issue.
Sam
I,
don't
have!
No.
If
you
have
anything
else
to
add
to
that.
F
F
I
believe
tomorrow,
actually
so
still
some
time
for
feedback
on
that.
If
you,
if
you
have
a
have
any
of
it
and
Tim,
looks
like
you've
got
the
next
one.
E
Yes,
if
I
find
my
unmute
button,
so
I
watched
a
recording
from
yesterday's
front
and
discussion
in
the
front
and
sync
where
it
was
a
lot
about
how
much
we
should
move
forward
versus
how
much
stuff
should
be
tied
up
and
how
big
Mr
should
be,
and
so
on,
and
so
I
wanted
to
basically
take
the
discussion
from
there
also
to
this
meeting
and
come
up
also
with
some
guidance
that
I
gave.
For
example,
Jan
that
I
believe
is
is
important
around
where
we
are
heading
and
how
fast
we
should
be
heading.
E
This
is
clearly
right.
Now
we
are
at
the
point
where
we
are
trying
to
deliver
something
for
internal
usage,
only
and
basically
starting
to
experiment
with
it,
and
we
are
exploring
also
a
lot
of
things
that
are
definitely
not
yet
on
anyone's
radar
and
you
can
find
out
by
the
implementation
already
a
lot
of
the
things.
So
my
my
general
guidance
around
stuff
that
needs
to
be
merged
is
always
code
wise.
It
has
to
be
production
quality
if
it
goes
into
into
Master.
E
It
needs
to
be
production
quality,
nothing
around
the
code
itself,
so
it
shouldn't
affect
anything
else.
It
shouldn't
be
taking
any
shortcuts.
In
that
sense,
it
should
be
there
and
complete
and,
following
all
the
guidelines
function,
buyers.
E
It
definitely
can
be
that
it's
as
long
as
it's
not
public
that
it
doesn't
have
fully
tied
up
all
the
ends
and
it's
completely
fully
functional.
So
this
means
like
that,
if
you
click
save
right
now,
you
will
not
get
basically
an
actual,
save,
but
we'll
see
the
code
display
and
we
shouldn't
build
some
workarounds
now
for
the
next
one
or
two
months
in
the
sense
of
building
something
that
explains
you
for
five
hours.
E
It's
clear
that
we
will
have,
especially
during
this
integration
phase,
which
is
a
classic
problem
of
starting
Green
Field
work
with
especially
large
Mrs,
that
if
you
tend
to
have
very
small
Mrs,
the
problem
is
that
you
have,
of
course
that
kind
of
overhead,
and
that
also
means
that
you
will
have
a
lot
of
unlogical
Mrs
as
I
call
them,
because
you
have
a
functional
that
you
can't
test,
which
is
also
taking
more
time
than
most
of
the
time
to
figure
out
so
I
think.
E
It's
also
important
that
we
simply
can
have
ends
that
simply
have
currently
a
constant
init
option
Etc,
and
we
should
always
have
to
focus
on
smaller
Mars.
But
it's
created
also
simply
setting
something
up
will
have
a
larger
Mr,
simply
implied
to
get
something
moving.
Otherwise,
you
will
end
up
with
and
logical
Mrs
to
really
just
code
blocks
that
don't
do
anything
that
are
not
usable
that
are
not
testable
on
the
spot,
but
I
already
rather
just
there
and
which
also
work
for
bigger
features.
E
C
E
Everything
that
we
are
doing
right
now
will
be
reworked
and
reiterated
anyhow,
but
it
should
definitely
have
the
target
to
be
usable
and
shipped
it's.
It's
definitely
clear
this,
especially
as
we
don't
have
a
ux
counterpart.
The
level
of
detailed
and
polishness
might
be
something
that
will
definitely
increase
and
change
over
time,
but
it's
also
clear
that
some
things
that
we
Implement
right
now
anyhow
get
reworked,
because
we
figure
out
during
the
implementation
that
we
find
something
else
that
is
needed
and
we
need
to
get
it
there
first
to
figure
something
out.
E
A
good
example
is,
if
you
look
at
the
data
table
that
just
landed
the
data
table
right
now
is
nice
because
it
gives
you
a
list
of
data,
but
is
it
usable
is
it
will
feel
people
have
the
feeling
that
this
is
is
great,
no
most,
probably
not,
because
the
URLs
are
cut.
You
can't
click
on
them.
You
can't
copy
paste.
It
then.
D
E
I
think
have
a
very
clear
feedback:
loop
going
from
engineers
and
people
using
it
to
the
PMs
and
then
hopefully,
at
some
point
also
to
ux,
which
is
very
important
overall
and
seeing
and
taking
a
look
also
about
Sam
is
highlighting
here
with
the
signal
boosting.
This
is
a
huge
topic
for
gitlab
and
we
make
good
progress,
I'm
happy
with
the
progress
in
itself,
but
have
we
shipped
anything
not
really
have
we
shipped
anything
that
has
already
made
some
impression
now,
because
we
are
connecting
the
dots
here,
but
I
think
we.
E
We
have
the
possibilities
to
make
quite
a
nice
impact
on
one
end
in
the
sense
of
showing
something
that
we
are
Way
Beyond,
for
example,
a
monitoring,
dashboard
solution
that
was
implemented
in
the
past.
That
was
only
Yammer
based,
but
have
something
where
we
can
iterate
very
fast
and
to
some
extent
this
is
both
internally
and
externally.
E
Important
because
having
a
dashboard
that
has
two
line,
charts
and
account
is
for
the
outside
and
most
probably
not
the
thing
that
will
say:
hey
here's,
my
money,
take
my
money
and
I
think
this
is
to
some
extent
where
we
need
to
show
up
and
figure
out,
and
we
will.
This
is
a
classic
startup
phase,
where
we
might
also
pivot
and
figure
out
hey.
This
is
something
where
we
can
get
very
fast
too,
and
this
is
something
that
might
take
longer,
so
we
should
get
started
there
and
so
on.
E
So
I
think
it's
important
that
everyone
is
aware
of
that
and
we
are
moving
in
in
that
kind
of
way
to
to
get
to
results
that
are
making
a
splash
and
are
can
be
also
very
strategic.
Very
good
example
is
the
editing
of
dashboards.
I
think
this
is
maybe
not
as
important
for
analytics
right
now,
but
it's
super
important
for
optimize,
because
this
is
something.
If
you
look
at
the
threads,
you
have
almost
a
weekly
level.
E
A
Yeah
I
wanted
to
better
understand
the
I,
from
my
understanding
from
the
front-end
red
show
and
and
what
you're
saying
it
seems
like.
We've
we've
been
in
alignment
as
far
as
like
quality
versus
like
this
is
the
pace
of
iteration.
What
I
wanted
to
better
understand
is
that
you
mentioned
a
couple
times
like
the
line
charts
and
and
like
the
dashboards
that
they
stand,
maybe
aren't
providing
that
wow
factor
and
that's
why
we're
looking
at
things
like
the
query
designer.
A
But
you
know
how
does
that
work
with
our
values
in
terms
of
like
trying
to
pursue
boring
Solutions,
because
I
think
we
are
setting
the
stage
with
like
some
very
important
features
for
other
groups
like
editable
dashboards
and
schema
driven
dashboards
and
using
those
to
build
boring
Solutions.
But
then
you
know,
if
we're
trying
to
think
like
a
startup
and
then
go
for
bigger
features.
How
does
that
go
and
like
work
with
us
experimenting,
but
also
shipping
production
level
code?
A
It
just
seems
like
some
of
these
themes:
kind
of
fight
against
work
against
each
other.
E
I
think
the
the
best
alignment
is
the
early
kitlab
phase,
where
it
was
all
the
time
fried
like
a
test
balloon
in
a
certain
area,
get
this
to
a
version
that
is,
that
does
something
meaningful
and
then
try
to
get
the
next
test
balloon
running
and
see.
E
If
that's,
if
that
does
something
meaningful,
and
if
one
of
those
test
balloons
gets
a
lot
of
traction,
then
you
invest
even
more
so
having
a
widget
designer,
for
example,
to
on
one
hand,
explore
the
data,
but
also,
on
the
other
hand,
make
the
dashboards
really
editable
and
and
meaningful,
then
also
beyond
the
first
dashboard
that
we
are
going
to
provide
can
give
ask
the
feedback,
loop.
If
people
really
would
like
to
work
with
this
and
have
basically
more
detailed
statistics.
E
Around
hey
I
want
to
know
who,
from
the
United
States
is
looking
at
this
and
that
page
and
has
basically
definitions
on
this.
So
this
is
not
going
maybe
on
100
maturity
straight
away,
but
setting
basically
test
balloons
up
to
see
if
you
can
get
traction
and
Way
Beyond.
A
level
of
the
classic
startup
page
use
a
sign
up
page
with
my.
A
E
And
there's
nothing
behind
it,
so
I
think
we
we
are
already.
We
have
a
couple
of
Lego
Stones
here
that
might
especially
with
the
setup
that
we
have
with
you
that
are
very
easy,
adaptable
and
that's.
For
example,
the
the
widget
designing
stuff
is
like
really
easy
stuff
and
that's
where
it
can
then
get
the
impact
to
some
extent.
I
believe
so.
A
Then,
how
would
you
balance
then,
coming
composing
and
chasing
these
test
balloons
versus
actually
like
working
towards
the
plan
to
get
features
in
front
of
the
users,
because
I
feel
like
that's
what
the
internal
preview
and
the
customer
preview
are
about,
so
that
we
can
establish
the
feedback
loop
with
people
that
are
actually
using
it.
Beyond
just
ourselves.
I
I
do
agree
that
it's
good
to
experiment
and
get
those
test
balloons.
So
we
can
see
where
we
want
to
head
to
next,
but
there's
only
four
Engineers
on
the
team.
A
Of
why
we
haven't
shipped
is
because
we
didn't
really
have
that
much
engineering
capacity
for
the
first
few
months
of
the
team
being
put
together.
So
you
know
we're
we're
obviously
resource
constrained
that
hopefully
changes
with
the
investment
themes
for
next
year.
But
you
know
how
would
you
recommend
then
you
know
dude?
Are
you?
Do
we
suggest
moving.
E
These
things
like
integrating
the
widget
designer
or
no
I
think
it's.
It's
simply
important
that
that
we
take
into
consideration
to
have
that
reviewed
and
also
invest
time
into
getting
that
moving.
That's
why
I'm
working
if
I
have
time
on
stuff
that
is
way
step
number
three:
four,
after
the
actual
roadmap
I,
if
the
roadmap
that
you
have
currently
sketched
out
same
with
you,
if
I
wouldn't
agree
to
it,
I
would
I
would
shout
basically
I
think
this
is
exactly
where
we
want
to
be
heading.
E
But
it
should
be
also
clear
that
while
we
are
heading
in
that
direction,
we
need
to
have
a
certain
kind
of
pace
and
basically
also
highlight
if
we
can
take
something
faster
or
slower
or
if
something
takes
longer,
so
that
we
can
have
this
amount
of
output
at
the
end
of
the
day.
I
think
that's
the
that's.
The
main
topic
here
is
to
see
if
we
see
that
something
takes
much
longer
that
we
highlight
this
so
that
we
have
this
drive
forward
around
the
work
that
we
are
classically
sketching
out
and
I.
E
Think
that's
totally
fine
and
it's
good,
but
that's
where
I'm
trying
to
connect
now
the
dots
more
and
with
manage
Optima
plan
optimized
by
now
that
they
are
also
starting
to
work
actively
on
the
dashboard
editing,
for
example,
and
where
can
we
number
0.8
is
really
about
exactly
one
of
those
shortcuts
and
what
you
think
about
it
that
we
can
take
that
so.
A
F
Iteration
means
that
we're
going
to
take
small
steps,
but
it
doesn't
mean
that
we
don't
have
a
longer
term
goal
of
where
we
ultimately
want
to
get
to
some
of
the
things
Tim's
mentioned
about
like
wow
factors
and
things
we
want
to
do
in
the
future.
That's
where
we
want
to
get
to,
but
also
like
we
talked
about,
we
haven't
shipped
anything
to
customers
or
to
end
users.
Yet
those
are
our
first
steps
and
we
need
to
take
boring
solutions
to
get
there.
F
One
of
the
the
hard
things
I
think
and
I
don't
I
haven't
read
the
the
notes
from
that
front.
I
mean
so
maybe
I'll
talk
through
some
of
this,
but
I
I
think
one
of
the
challenges
with
our
iteration
values
to
be
able
to
identify
here's.
What
our
long-term
vision
is
that
we're
ultimately
going
to
work
towards
versus
these
are
the
Tactical
steps
we
need
to
do
today
as
the
first
small
iteration
to
get
us
closer
to
that.
F
So
doing
things
like
the
internal
preview
are
going
to
be
critical
so
that
we
get
something
out
to
internal
users.
Then
the
customer
preview
of
we
get
something
out
to
end
customers
that
they
can
use
with
our
ultimate
long-term
Vision.
Being
this,
you
know,
amazing,
completely
perfect
thing
that
will
take
more
time
to
realize
along
the
way.
D
Yeah
and
I
can
Echo
a
bit
of
what
I
mentioned
yesterday.
That
I
said
that-
and
this
is
maybe
not
as
as
related
but
I
do
believe.
We
are
in
a
in
a
good.
E
E
So
I
think
we
discussed
this
two
weeks
ago
around
a
solution
also
with
the
plane
optimize
group
so
to
Simply,
have
like
a
pointer
to
a
project
where
the
dashboards
are
stored
and
using
the
API
would
enable
us
to
Simply,
say:
okay,
we
have
a.
We
just
have.
Basically
the
project
ID
would
give
enough
for
the
front
end
to
go
ahead.
Have
eight
dashboards,
editable
and
savable
have
widgets
editable
and
savable
through
that
API,
but
of
course
it
doesn't
send
it
through
the.
C
E
Is
to
go
ahead
and
that
we
take
a
look.
Can
we
really
do
this
and
simply
take
a
fixed
director
on
a
different
repo
as
a
first
step,
because
I
believe
that,
as
we
are
constrained
with
Max
on
the
backend
side,
I
rather
would
like
to
see
him
on
funnels
and
such
topics
and
I'm
quite
clear
that
you
will
agree
on
that.
So.
E
And
then
in
a
phase,
two
replaced
it
with
having
a
centered
point
in
the
front
and
called
part
which
basically
takes
okay,
that's
dashboard,
save
it
with
that
name,
that's
which
you'd
save
it
with
that
name
and
basically
replace
that
central
part
against
specific
API
at
some
point.
E
A
B
I
think
when
you
say
using
the
commit
API,
you
mean
emitting
generating
the
Json
for
the
dashboard
and
committing
it
on
their
behalf
or
creating
an
MR
for.
C
E
B
Yeah
that
that's
the
thing
my
concern
is
like,
yes,
from
a
usability
point
of
view,
the
fewer
barriers
to
getting
dashboards
updated
the
better.
However,
there
are
so
many
ways
in
which
an
MR
can
be
held
up
like
code
owners,
approval
rules,
external
status
checks
and
we're
we're
targeting
git
that
ultimate
initially
at
least-
and
these
are
the
customers
with
the
most
stringent
compliance
requirements
and
I
worry
that
we're
setting
a
dangerous
precedent
by
saying
yes,
you
must
always
put
changes
through
a
full
Mr
approval
processes.
B
Oh
except
in
this
case,
I
worry
that
that
won't
be
well
tolerated.
No.
E
C
I'm
still
questioning
the
the
the
the
whether
some
ultimate
customers
in
very
stringent
compliance
environments
would
even
allow
that
to
happen.
Still
feels
quite
I
still
feel
like.
There
are
some
which
would
need
that
chain
of
custody,
and
they
need
that
step
where
the
where
someone
else
has
proved
confirmed
that
what
they're
doing
is
valid
a
bit
like
we
don't
just
let
anyone
edit
our
cisense
dashboards.
C
There
are
some
which
are
proper
restricted
because
it's
unsafe
data,
so
in
my
head,
that's
where
I
I
sort
of
feel
like
I
would
rather
go
on
the
the
side
of
caution
and
have
everything
an
MR
and
then
introduce
the
ability
to
go
direct
to
commit
than
the
other
way
around.
If
that
makes
sense,.
E
The
problem
is
really
with
them
ours.
This
becomes
to
some
extent,
especially
for
experimenting
at
the
beginning,
a
usability
nightmare
I.
F
In
terms
of
iterating
and
boring
Solutions,
what
I
would
suggest,
since
we
are
over
time
at
this
point-
is
that
we
go
with
having
just
you
know.
We
show
just
the
code
today
we
do
the
existing
Mr
flow.
If
we
get
feedback
that
it
is
going
to
provide
a
lot
of
friction
for
users
that
want
to
do
experimenting,
then
we
can
also
look
at
what
those
ultimate
level
customers
would
need
to
do
more
of
a
directly
committing
workflow,
but
I
I.
Think
if
we
have
our
first
step
being
you
go
through
a
merch.
E
E
This
makes
it
10
times
more
complex,
any
sort
of
Mr,
but
I
I'm
happy
that
we
can
to
have
a
graph
and
play
it
through,
but
editing
with
Mrs
in
between
becomes
horrible
complex
in
a
complete
new
eye,
I
noticed
still
from
the
web
ID
times
when
they
started
I
think
it
took
them
four
months
to
implement
there,
the
workflow
of
having
Mrs
and
not
being
able.
So
this
this
makes
basically
suddenly
saving
and
adding
new
stuff
four
months
out.
F
Well,
because
of
the
complexity
about
this
I
think
this
is
definitely
one
of
the
areas
we
need
to
have
ux
research
look
into
and
propose
different
solutions
to
figure
out,
where's
that
sweet
spot
between
security
and
compliance
concerns
versus
ease
of
use,
and
where
do
we
end
up
ultimately
Landing
there,
like
Rob,
said
we
don't
have
a
ux
person
to
start
on
that
right
now,
so
this
could
be
something
they
could
jump
into
in
the
new
year
as
well.
E
That
ux
person
is
months
out,
so
I
would
rather
say
April
before
they
can
start
yeah.
We
can
discuss
this
good.
Do
we
have
anything
else
that
we
want
to
go
through
because
I've
got.
E
Yeah
and
adding
the
additional
tracking
I
will
take
this
most
prior
to
the
product
intelligence
team
directly
that
they
get
started
on
that
for
Habitat,
so
that
we
get
right
now,
but
we
are
only
collecting
on
the
internal
handbook
is
just
page
views,
but
we
should
have
also
click
events,
data
and
also
get
product
area,
IDs
and
stuff
like
that,
so
that
we
can
play
around
with
that
part
good
good,
good,
good
good,
then
thanks.
Everybody.