My Projects
Home
Free AI SMART Goals Generator
SMART Work Goals
1 / 10
SMART
Work
Goals
2 / 10
01
Goals
at
a
glance
The
twelve
goals
below
are
grouped
by
intent
.
Read
this
list
first
—
the
SMART
breakdowns
that
follow
expand
each
item
without
changing
its
scope
.
A
·
P E R F O R M AN C E
&
DE L IVE R Y
01
Cut
median
ticket
resolution
time
from
14.2
hours
to
under
6
hours
by
30
September
2026.
02
Migrate
the
legacy
billing
worker
to
the
managed
queue
with
zero
customer
-
visible
downtime
and
retire
the
legacy
service
by
30
September
2026.
03
Lift
net
revenue
retention
on
the
mid
-
market
book
from
104%
to
112%
by
31
December
2026.
B
·
G R O WT H
&
C APAB IL IT Y
01
Earn
the
AWS
Certified
Solutions
Architect
–
Professional
certification
by
30
June
2026.
02
Complete
40
structured
discovery
interviews
with
frontline
support
agents
between
February
and
September
2026.
03
Deliver
4
internal
brown
-
bag
sessions
on
queueing
and
data
modelling
,
each
rated
4.0
or
higher
,
by
15
December
2026.
C
·
L E ADE R S HIP
&
C O L L AB O R AT IO N
01
Mentor
two
junior
operations
analysts
through
their
first
end
-
to
-
end
production
ownership
rotation
by
31
October
2026.
02
Reduce
recurring
cross
-
team
status
meetings
from
5
per
week
to
2
per
week
by
31
March
2026,
replacing
the
rest
with
written
updates
.
03
Publish
a
quarterly
written
operating
review
that
90%
of
stakeholders
rate
as
useful
in
a
two
-
question
survey
.
D
·
P R O C E S S
&
IN N O VAT IO N
01
Reduce
CI
pipeline
runtime
from
22
minutes
to
under
8
minutes
on
the
main
branch
by
31
July
2026.
02
Launch
a
self
-
serve
onboarding
flow
that
lifts
week
-
one
activation
from
38%
to
55%
by
30
November
2026.
03
Cut
cloud
spend
per
active
customer
by
18%
without
degrading
p
95
API
latency
beyond
180
ms
by
31
December
2026.
3 / 10
02
Goals
in
SMART
detail
Each
goal
is
broken
down
against
Specific
,
Measurable
,
Achievable
,
Relevant
and
Time
-
bound
.
Baselines
are
drawn
from
the
Q
4
FY
2025
operations
review
unless
stated
otherwise
.
01
Cut
median
ticket
resolution
time
from
14.2
hours
to
under
6
hours
A
·
Performance
&
Delivery
·
Baseline
: 14.2
h
median
,
Q
4
FY
2025
S P EC IFIC
What
exactly
Redesign
the
tier
-1
triage
model
in
our
helpdesk
so
billing
and
account
-
access
tickets
route
directly
to
a
trained
specialist
queue
instead
of
the
general
pool
,
and
remove
the
mandatory
escalation
approval
step
for
refunds
under
$
250.
MEAS UR ABL E
How
we
count
Median
time
from
ticket
creation
to
resolution
,
reported
weekly
from
the
operations
dashboard
.
Target
:
≤
6.0
hours
sustained
for
four
consecutive
weeks
.
Secondary
check
:
p
90
resolution
under
30
hours
.
AC HIEVABL E
Why
it
holds
The
Q
3
FY
2025
billing
-
queue
pilot
cut
resolution
time
by
41%
with
two
additional
senior
analysts
on
rotation
,
which
shows
the
routing
change
—
not
headcount
—
is
the
binding
constraint
.
R EL EVANT
Why
it
matters
Ticket
backlog
was
the
single
most
cited
reason
for
cancellation
in
Q
4
exit
interviews
,
and
slow
resolution
is
associated
with
roughly
$
18,000
of
at
-
risk
ARR
per
month
.
T IME
-
BOUND
When
New
triage
rules
live
by
15
April
2026.
Six
-
hour
median
sustained
by
30
September
2026.
02
Migrate
the
legacy
billing
worker
with
zero
customer
-
visible
downtime
A
·
Performance
&
Delivery
·
Owner
:
Platform
Operations
S P EC IFIC
What
exactly
Move
the
invoice
-
generation
worker
off
the
single
-
region
,
end
-
of
-
life
runtime
and
onto
the
managed
queue
with
a
blue
-
green
cutover
,
then
decommission
the
legacy
service
and
its
two
cron
jobs
.
MEAS UR ABL E
How
we
count
Zero
Sev
1
or
Sev
2
incidents
during
cutover
;
100%
of
invoices
reconciled
line
-
for
-
line
against
legacy
output
for
two
full
billing
cycles
;
job
error
rate
under
0.05%
.
AC HIEVABL E
Why
it
holds
The
staging
cutover
in
November
2025
ran
clean
across
three
simulated
billing
cycles
,
and
the
reconciliation
script
is
already
in
the
repository
and
covered
by
tests
.
R EL EVANT
Why
it
matters
The
legacy
runtime
reaches
end
of
security
support
in
October
2026,
and
a
billing
failure
is
the
one
outage
category
that
directly
blocks
customer
revenue
collection
.
T IME
-
BOUND
When
Production
cutover
by
31
July
2026.
Reconciliation
window
closes
and
legacy
service
retired
by
30
September
2026.
4 / 10
03
Lift
mid
-
market
net
revenue
retention
from
104%
to
112%
A
·
Performance
&
Delivery
·
Baseline
: 104%
NRR
,
trailing
12
months
S P EC IFIC
What
exactly
Introduce
a
90-
day
post
-
sale
check
-
in
sequence
for
mid
-
market
accounts
and
a
tiered
usage
-
based
expansion
offer
triggered
at
80%
seat
utilisation
,
targeting
the
140
accounts
between
$
15
K
and
$
60
K
ARR
.
MEAS UR ABL E
How
we
count
Trailing
-
twelve
-
month
net
revenue
retention
on
the
defined
mid
-
market
segment
,
measured
monthly
in
the
finance
model
.
Target
:
112%
by
year
end
,
with
gross
churn
held
at
or
below
6%
.
AC HIEVABL E
Why
it
holds
Expansion
revenue
already
grew
9%
quarter
over
quarter
in
the
two
pilot
regions
where
the
check
-
in
sequence
ran
,
and
the
seat
-
utilisation
trigger
has
not
yet
been
offered
to
any
account
.
R EL EVANT
Why
it
matters
Mid
-
market
accounts
represent
46%
of
recurring
revenue
and
the
highest
support
cost
per
dollar
,
so
improving
retention
there
compounds
faster
than
new
-
logo
acquisition
.
T IME
-
BOUND
When
Check
-
in
sequence
live
by
1
May
2026.
Expansion
offer
rolled
out
to
all
regions
by
31
August
2026.
Target
measured
at
31
December
2026.
04
Earn
the
AWS
Certified
Solutions
Architect
–
Professional
certification
B
·
Growth
&
Capability
·
Development
goal
S P EC IFIC
What
exactly
Pass
the
AWS
Certified
Solutions
Architect
–
Professional
exam
and
complete
the
associated
four
-
module
advanced
architecture
curriculum
,
with
a
written
summary
of
two
exam
domains
applied
to
our
own
infrastructure
.
MEAS UR ABL E
How
we
count
One
passing
exam
result
on
file
,
plus
a
practice
-
exam
score
of
85%
or
higher
before
booking
the
real
exam
,
and
a
two
-
page
internal
write
-
up
delivered
to
the
platform
team
.
AC HIEVABL E
Why
it
holds
The
learning
budget
covers
the
exam
fee
and
the
prep
course
,
and
90
minutes
are
reserved
on
Friday
afternoons
through
Q
2
for
study
without
competing
delivery
commitments
.
R EL EVANT
Why
it
matters
The
billing
migration
and
cost
-
optimisation
goals
both
depend
on
multi
-
region
and
queueing
design
decisions
,
and
this
is
the
credential
the
architecture
review
board
expects
on
the
team
.
T IME
-
BOUND
When
Curriculum
finished
by
15
May
2026.
Exam
sat
and
passed
by
30
June
2026.
5 / 10
05
Complete
40
structured
discovery
interviews
with
frontline
support
agents
B
·
Growth
&
Capability
·
Research
goal
S P EC IFIC
What
exactly
Run
45-
minute
semi
-
structured
interviews
with
support
agents
across
all
three
regions
,
using
a
fixed
question
guide
covering
tooling
friction
,
escalation
paths
and
knowledge
gaps
,
and
tag
every
transcript
against
a
shared
themes
file
.
MEAS UR ABL E
How
we
count
40
completed
interviews
logged
,
100%
transcribed
and
tagged
,
and
two
synthesis
reports
delivered
—
one
at
the
midpoint
and
one
at
close
.
AC HIEVABL E
Why
it
holds
Two
interviews
per
week
is
roughly
three
hours
of
scheduled
time
,
which
fits
inside
the
current
research
allocation
and
does
not
require
backfill
coverage
.
R EL EVANT
Why
it
matters
The
resolution
-
time
and
onboarding
goals
both
assume
we
know
where
agents
lose
time
;
that
assumption
has
never
been
tested
with
primary
research
at
this
scale
.
T IME
-
BOUND
When
First
20
interviews
by
30
April
2026.
Remaining
20
complete
and
synthesis
published
by
30
September
2026.
06
Deliver
four
internal
brown
-
bag
sessions
on
queueing
and
data
modelling
B
·
Growth
&
Capability
·
Knowledge
-
sharing
goal
S P EC IFIC
What
exactly
Prepare
and
present
four
40-
minute
internal
sessions
—
message
queues
and
backpressure
,
event
ordering
,
normalising
the
support
data
warehouse
,
and
reading
an
explain
plan
—
each
with
a
written
takeaway
page
.
MEAS UR ABL E
How
we
count
Four
sessions
delivered
,
average
attendance
of
at
least
15
colleagues
,
and
a
post
-
session
rating
of
4.0
or
higher
out
of
5
on
a
one
-
question
form
.
AC HIEVABL E
Why
it
holds
Two
sessions
were
already
delivered
in
FY
2025
at
an
average
rating
of
4.3,
so
the
format
and
the
room
are
proven
;
only
the
material
needs
refreshing
.
R EL EVANT
Why
it
matters
Six
analysts
joined
the
team
in
the
last
year
,
and
the
warehouse
modelling
standard
is
currently
documented
nowhere
outside
one
person
'
s
notes
.
T IME
-
BOUND
When
Two
sessions
by
30
June
2026,
two
more
by
15
December
2026,
each
at
least
eight
weeks
apart
.
6 / 10
07
Mentor
two
junior
analysts
through
their
first
production
ownership
rotation
C
·
Leadership
&
Collaboration
·
People
goal
S P EC IFIC
What
exactly
Take
two
analysts
who
have
not
yet
held
an
on
-
call
or
incident
-
ownership
rotation
and
guide
each
through
one
full
production
ownership
cycle
,
including
a
written
runbook
they
author
themselves
.
MEAS UR ABL E
How
we
count
Two
analysts
complete
a
full
rotation
,
each
authors
an
approved
runbook
,
and
both
rate
the
mentorship
4.0
or
higher
on
confidence
in
handling
an
incident
alone
.
Fortnightly
one
-
hour
sessions
logged
.
AC HIEVABL E
Why
it
holds
The
rotation
structure
already
exists
and
has
been
used
successfully
by
the
platform
team
;
the
work
is
in
pairing
and
review
,
not
in
building
a
new
programme
.
R EL EVANT
Why
it
matters
Single
-
person
dependency
on
incident
response
is
the
top
risk
flagged
in
the
last
continuity
review
,
and
the
team
plans
to
hire
two
more
analysts
next
year
.
T IME
-
BOUND
When
First
analyst
paired
by
1
May
2026,
second
by
1
July
2026.
Both
rotations
complete
by
31
October
2026.
08
Reduce
recurring
cross
-
team
status
meetings
from
five
per
week
to
two
C
·
Leadership
&
Collaboration
·
Focus
goal
S P EC IFIC
What
exactly
Audit
every
recurring
meeting
on
the
operations
calendar
,
cancel
or
convert
at
least
three
of
the
five
weekly
synchronisations
into
a
written
async
update
,
and
keep
one
standing
review
plus
one
open
clinic
.
MEAS UR ABL E
How
we
count
Recurring
meeting
count
drops
from
5
to
2
per
week
on
the
shared
calendar
,
average
weekly
meeting
hours
fall
below
4
,
and
no
more
than
two
written
updates
are
missed
in
a
quarter
.
AC HIEVABL E
Why
it
holds
The
January
audit
already
identified
three
meetings
with
no
decisions
recorded
in
twelve
weeks
,
which
makes
them
the
obvious
first
conversions
.
R EL EVANT
Why
it
matters
Written
updates
reach
colleagues
in
three
time
zones
who
cannot
attend
the
current
slots
,
and
reclaimed
hours
go
directly
toward
the
resolution
-
time
and
onboarding
goals
.
T IME
-
BOUND
When
Audit
complete
by
28
February
2026.
New
cadence
running
and
holding
at
two
meetings
per
week
by
31
March
2026.
7 / 10
09
Publish
a
quarterly
written
operating
review
rated
useful
by
90%
of
stakeholders
C
·
Leadership
&
Collaboration
·
Communication
goal
S P EC IFIC
What
exactly
Write
and
circulate
a
four
-
page
operating
review
each
quarter
covering
performance
against
target
,
the
three
biggest
operational
risks
,
decisions
needed
from
leadership
,
and
one
retrospective
note
on
what
did
not
work
.
MEAS UR ABL E
How
we
count
Four
reviews
published
within
five
working
days
of
quarter
close
,
each
with
an
average
usefulness
score
of
90%
or
higher
across
a
two
-
question
stakeholder
survey
(
n
≈
22).
AC HIEVABL E
Why
it
holds
A
draft
format
already
exists
from
the
Q
4
FY
2025
review
,
which
scored
82%
on
the
same
survey
;
the
gap
is
consistency
of
publication
,
not
the
underlying
content
.
R EL EVANT
Why
it
matters
Leadership
currently
learns
about
operational
risks
during
incidents
rather
than
in
advance
,
and
the
review
is
the
cheapest
available
fix
for
that
.
T IME
-
BOUND
When
First
review
by
5
April
2026,
then
within
five
working
days
of
each
quarter
close
through
31
December
2026.
10
Reduce
CI
pipeline
runtime
from
22
minutes
to
under
8
minutes
D
·
Process
&
Innovation
·
Efficiency
goal
S P EC IFIC
What
exactly
Profile
the
main
-
branch
pipeline
,
parallelise
the
integration
test
suite
,
introduce
dependency
and
build
-
layer
caching
,
and
remove
the
two
redundant
end
-
to
-
end
suites
that
duplicate
coverage
already
handled
upstream
.
MEAS UR ABL E
How
we
count
Median
pipeline
duration
on
the
main
branch
measured
over
a
rolling
seven
days
.
Target
:
under
8
minutes
,
sustained
for
one
month
,
with
test
coverage
held
at
or
above
the
current
81%
.
AC HIEVABL E
Why
it
holds
Parallelising
the
integration
suite
alone
is
estimated
to
save
about
nine
minutes
based
on
the
profiling
run
completed
in
January
,
and
the
caching
change
is
a
configuration
edit
.
R EL EVANT
Why
it
matters
Slow
pipelines
are
the
second
most
cited
friction
point
in
the
developer
survey
,
and
the
billing
migration
depends
on
fast
,
trustworthy
pre
-
merge
feedback
.
T IME
-
BOUND
When
Profiling
and
caching
by
30
April
2026.
Parallelisation
and
suite
cleanup
by
30
June
2026.
Eight
-
minute
median
sustained
by
31
July
2026.
8 / 10
11
Launch
a
self
-
serve
onboarding
flow
that
lifts
week
-
one
activation
to
55%
D
·
Process
&
Innovation
·
Growth
goal
·
Baseline
: 38%
week
-
one
activation
S P EC IFIC
What
exactly
Replace
the
current
manual
setup
call
with
a
guided
in
-
product
onboarding
flow
—
workspace
import
,
first
-
integration
connect
,
and
a
seeded
sample
dashboard
—
available
without
contacting
support
.
MEAS UR ABL E
How
we
count
Share
of
new
accounts
completing
the
three
activation
steps
within
seven
days
of
signup
.
Target
:
55%
,
up
from
38%
.
Secondary
:
support
-
assisted
onboarding
requests
fall
by
30%
.
AC HIEVABL E
Why
it
holds
A
six
-
week
prototype
on
the
self
-
serve
tier
reached
47%
activation
in
a
limited
rollout
,
and
the
import
tooling
behind
it
is
already
production
-
ready
.
R EL EVANT
Why
it
matters
Accounts
that
reach
activation
within
a
week
renew
at
roughly
twice
the
rate
of
those
that
do
not
,
and
manual
onboarding
currently
consumes
38
hours
of
team
time
per
month
.
T IME
-
BOUND
When
Flow
built
and
internally
tested
by
31
July
2026.
Full
rollout
by
30
September
2026.
Target
measured
at
30
November
2026.
12
Cut
cloud
spend
per
active
customer
by
18%
without
degrading
latency
D
·
Process
&
Innovation
·
Cost
goal
·
Baseline
:
$
0.41
per
active
customer
per
day
S P EC IFIC
What
exactly
Right
-
size
the
three
over
-
provisioned
compute
clusters
,
move
the
analytics
workloads
to
scheduled
off
-
peak
batch
runs
,
and
apply
storage
lifecycle
policies
to
move
logs
older
than
45
days
to
cold
storage
.
MEAS UR ABL E
How
we
count
Total
monthly
cloud
spend
divided
by
active
customers
,
tracked
against
the
finance
baseline
of
$
0.41
per
customer
per
day
.
Target
:
$
0.34
,
a
reduction
of
18%
,
with
p
95
API
latency
held
under
180
ms
.
AC HIEVABL E
Why
it
holds
The
January
cost
review
identified
$
41,000
of
annualised
waste
in
idle
cluster
capacity
alone
,
which
is
roughly
two
thirds
of
the
total
target
.
R EL EVANT
Why
it
matters
Gross
margin
is
the
board
'
s
headline
metric
for
the
year
,
and
infrastructure
is
the
largest
single
line
item
under
cost
of
goods
sold
.
T IME
-
BOUND
When
Right
-
sizing
complete
by
31
May
2026.
Batch
migration
and
lifecycle
policies
by
31
August
2026.
Eighteen
-
percent
reduction
held
for
two
consecutive
months
by
31
December
2026.
9 / 10
03
Review
cadence
Goals
are
live
documents
.
These
checkpoints
keep
the
baseline
honest
without
renegotiating
scope
mid
-
cycle
.
CHECKPO INT
WHEN
O WNER
WHAT
HAPPENS
Monthly
self
-
check
Last
Friday
Goal
owner
Update
each
metric
in
the
goals
tracker
and
flag
any
goal
tracking
more
than
10%
off
plan
.
Quarterly
review
5
April
· 5
July
· 5
October
Manager
Thirty
-
minute
review
of
progress
against
each
target
,
with
written
notes
added
to
the
operating
review
.
Mid
-
year
recalibration
1–15
July
2026
Manager
+
People
Partner
Baselines
may
be
adjusted
only
where
the
underlying
business
assumption
changed
;
the
target
itself
is
not
lowered
.
Year
-
end
assessment
15–31
December
2026
Manager
+
Director
Final
measurement
against
each
target
,
with
evidence
attached
for
every
metric
claimed
as
met
.
10 / 10
