►
From YouTube: 3 responsibilities every software startup should address
Description
In this 15 minute video, Tom Wilson discusses what a CTO role can look like for a Software Startup. You can find out more information about fractional CTO services and a deeper dive into CTO services by subscribing to this channel or joining us on slack. https://hyper.io/slack - #cto channel
https://blog.hyper.io/cto-for-startups/
A
A
The
architecture
is
how
the
code
is
organized
so
that,
as
your
team
grows,
as
your
features
grow,
that
there's
clarity
in
where
things
go
and
and
where
things
are
maintained
in
terms
of
life
cycle,
that
is
from
idea
to
user
right,
the
whole
process
of
going
from
here's
an
idea.
How
do
we
implement
that
verify
that
and
ship
that
to
our
user
to
use?
And
then
we
create
this
feedback
loop
so
that
we're
constantly
learning
and
innovating
to
provide
the
best
possible
functionality
for
that
user?
A
The
third
is
to
meet
and
work
with
customers,
prospects
leaders,
stakeholders
to
help
provide
clarity
and
understanding
of
the
technical
abilities
and
capabilities
of
the
products
and
the
team.
This
is
what
many
people
call
user
experience,
but
the
more
that
you
can,
you
know,
provide
clarity
on
how
the
problem
is
being
defined
and
how
the
solution
is
working
in
a
way
to
create
to
to
create
clarity
in
the
outcomes
for
the
user.
So
they're
satisfied
when
they're
paying
for
this
value
that
that
value
is
being
delivered.
A
A
The
main
gist
of
this
is
to
establish
values,
and
these
you
hear
of
core
values
within
a
company,
but
you
have
values
within
a
technology
group.
These
values
really
perform
the
guidelines
of
decision
making
within
the
group.
There's
four
core
values
presented
in
the
agile
manifesto,
which
are
are
really
kind
of
the
standard
starting
point
for
for
any
technology.
A
Team's
values-
and
I
you
know
we'll,
leave
a
link
in
in
the
video
for
you
to
to
visit
that,
but
there's
some
additional
values
to
consider
to
to
get
down
on
paper,
and
it's
highly
effective
to
do
this
with
the
technology
team,
so
that
there
is
a
complete
exploration
and
kind
of
collaboration
around
these.
But
here
are
four
that
I
find
really
really
valuable
to
get
down
on
paper
integrity,
commitment
to
quality.
What
does
that
mean?
What
does
that
mean
to
the
team
and
to
the
organization
automate
repeatable
operations?
A
A
It's
it's
hard
to
keep
software
simple,
especially
when
you're
building
complex
software.
So
how
can
we
do
that?
One
one
strategy
is
functional
thinking
and
there's
several
other
strategies
to
to
debate
and
go
through,
but
but
if
you
as
a
technology
group,
establish
these
values,
then,
as
you
progress
into
practices
and
processes,
operations
policies,
you
have
these
guidelines
to
lead
you
in
the
right
direction:
to
create
high
value
and
high
quality
for
your
company,
a
clear
vision
of
the
software
architecture
and
software
delivery
cycle.
A
Maybe
the
the
leaders
aren't
quite
as
technical
or
maybe
the
developers
are
not
highly,
have
a
high
degree
of
experience
in
working
with
within
startup
cultures,
so
to
explicitly
sit
down
and
establish
a
vision
and
purpose
for
the
technology
group
can
really
work
to
bridge
that
gap.
There's
a
tool
that
I
use
quite
often
called
the
inception
deck
and
it's
from
the
agile
samurai
book,
and
it's
just
10
questions.
A
What's
the
pros
and
cons
of
that
pattern,
what
are
the
trade-offs
and
making
that
clear,
as
a
technology
group
is
hugely
important?
I
think
clean
architecture.
Does
this
really
really
well,
but
but
there's
other
patterns
to
to
discuss
the
the
main
point
is:
is
clarity
and
when
your
technology
team
has
clarity
on
what
their
expectations
are,
it
is.
A
It
removes
so
much
of
the
impedance
to
to
get
things
done
over
time
and,
finally,
the
third
responsibility
is
to
meet
and
work
with
customers
and
prospects
to
help
provide
clarity
and
understanding
of
technical
abilities
and
capabilities
of
the
company
software
products.
So
this
is
a
big
sentence
that
basically
means
empathy
as
a
cto.
A
You
need
to
understand
the
customer
as
deeply
as
you
possibly
can
now
that
doesn't
mean
if
your
customer
is
a
doctor
that
you
have
to
become
a
doctor.
What
it
means,
though,
is
is
you
need
to
understand
why
they
would
be
interested
in
this
product?
What
value
does
it
provide
to
that
customer
so
that
they're
willing
to
pay
for
the
product
and
what
outcomes
do
they
need
to
know
that
this
product
is
providing
that
value
that
they
are
purchasing
so,
whether
it's
in
presentations
or
whether
it's
in
meetings?
A
So
with
that,
I
just
wanted
to
go
through
you
know.
Hopefully
this
presentation
gives
you
some
insight
on.
You
know
why
should
a
startup
think
about
having
a
cto
role
as
well
as
what
are
the
responsibilities
that
that
cto
would
provide
and
be
accountable
for
in
in
order
to
provide
value
to
your
organization
and
company?