Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
MAKE POST-
LAUNCH A
SUCCESS Ground Control 2017

Natalie Semczuk

@talkanatalka
Hello
LET’S TALK
PROJECTS
A QUICK
STORY…
THE WORST FEELING IS
HANDING OVER A
PROJECT THAT A CLIENT
CAN’T MAINTAIN
PROJECT
MANAGERS
HOLD THE KEYS
TO A PROJECT
OUR PROJECTS
HAVE
PROCESSES
• Project definition/start point

• Work on deliverables

• Test/refine

• Launch
WE INVOLVE OUR
CLIENTS AND
STAKEHOLDERS
• Discovery

• Scope

• Clarification

• Testing

• Demos

• Training
BUT WHAT ELSE
CAN WE DO?
POST-
LAUNCH
WHAT PIECES OF
CONTENT WILL
GET UPDATED?
DOES THE CLIENT
HAVE A TEAM IN
PLACE TO UPDATE
THE NEW SITE?
WHO ELSE IS
INVOLVED IN
MAINTENANCE
DECISIONS?
WHAT DOES THE
CONTENT
PROCESS LOOK
LIKE?
From decision to content creation
to approval to posting.
IS THERE A
DESIGN/
DEVELOPMENT
PLAN IN PLACE?
WHAT ABOUT
SECURITY, UPDATES,
AND
INFRASTRUCTURE
SUPPORT?
SOME CLIENTS
HAVE SOME OF THIS
COVERED. MOST
DON’T HAVE ALL.
WE CAN REVERSE ENGINEER
OUR PROCESSES TO
INCLUDE
EDUCATION +
EXPECTATIONS
PRE-
PROJECT
Activity
WHAT QUESTIONS
MIGHT YOU ASK
ABOUT SITE &
CONTENT
MANAGEMENT?
Activity
THE
IMPORTANCE
OF DISCOVERY
SET
EXPECTATIONS
ABOUT POST-
LAUNCH BY
ASKING UP-FRONT
GET THE STAKEHOLDER
TEAM ON BOARD WITH
THEIR
RESPONSIBILITIES
AFTER LAUNCH
FROM
DISCOVERY
TO PROJECT
PLANNING
GREAT
PROCESSES
ENCOURAGE
POST-LAUNCH
SUCCESS
CAPTURING
CONTENT MANAGER
WORKFLOWS
HELPS US DESIGN
& DEVELOP BETTER
CREATE A
CONTENT
WORKFLOW &
RESPONSIBILITIES
MAP
RACI MATRIX
FOR POST-
LAUNCH
PLANNING
RACI =
RESPONSIBLE
ACCOUNTABLE
CONSULTED
INFORMED
RESPONSIBLE
Who does the work to achieve the
task?
ACCOUNTABLE
Who is responsible for the correct
and thorough completion of the
task?
CONSULTED
Who provides information for the
project and communicates
regarding the tasks/projects?
INFORMED
Who needs to be informed of
progress and is affected by the
outcome of the tasks?
PRE-PLAN THE
MAINTENANCE
WORKFLOW
Activity
GET CLIENTS
THINKING
ABOUT THEIR
OWN PROCESS
MANAGE
EXPECTATIONS
ABOUT PROJECT
USE CASES FROM
THE START
SOME CAN
BE
EXTREMELY
SIMPLE:
OR IT COULD
BE MUCH
MORE
COMPLEX:
csffct.co/RGfGOu
PRE-
LAUNCH
GIVE CLIENTS
THE TOOLS
TO MANAGE
THEIR SITES
HOW CAN WE
ENSURE
THEY’RE
EDUCATED AND
PREPARED?
“PHASE 2”
ITERATIVE
PROCESSES
FEATURE
DEVELOPMENT
UPDATES/
MAINTENANCE
PACKAGES
TYPICAL
“LIFESPAN” OF A
WEBSITE
PROCESSES
NEED FEEDBACK
LOOPS
Planning —> Research —> Design —> Development —> Launch —> Maintenance
Planning —> Research —> Design —> Development —> Launch —> Maintenance
Planning —> Research —> Design —> Development —> Launch —> Maintenance
SETTING UP
PROJECTS FOR
POST-LAUNCH
SUCCESS REQUIRES
PLANNING
PRE-PROJECT
QUESTIONS AND
RESPONSIBILITY
PLANNING
DURING THE PROJECT,
CONTENT AND SITE
MANAGEMENT
WORKFLOWS MUST
BE CONSIDERED
POST-LAUNCH
EXPECTATION
SETTING, TRAINING,
AND UPKEEP
LEADS TO: MORE
MANAGEABLE WEBSITES,
MORE UPDATED CONTENT,
HAPPIER USERS ON BACK
AND FRONT END
THANK
YOU!
Natalie Semczuk

@talkanatalka

natalie@goodmerit.co

goodmerit.co

talkanatalka.com
Make post launch a success
Make post launch a success
Upcoming SlideShare
Loading in …5
×

Make post launch a success

1,616 views

Published on

Ground Control 2017 Talk.

It’s launch day! You and your team have worked hard to achieve this — the moment when you release your client’s website into the wild, ready to go off and live on its own. But wait! Is the client’s team equipped to handle the growing needs of their new website? Who will be making needed updates? Are other team members involved in content maintenance decisions? And will your client be able to deal with the design and development needs of the site as the site’s purpose grows?

Published in: Software
  • Be the first to comment

  • Be the first to like this

Make post launch a success

  1. 1. MAKE POST- LAUNCH A SUCCESS Ground Control 2017 Natalie Semczuk @talkanatalka
  2. 2. Hello
  3. 3. LET’S TALK PROJECTS
  4. 4. A QUICK STORY…
  5. 5. THE WORST FEELING IS HANDING OVER A PROJECT THAT A CLIENT CAN’T MAINTAIN
  6. 6. PROJECT MANAGERS HOLD THE KEYS TO A PROJECT
  7. 7. OUR PROJECTS HAVE PROCESSES • Project definition/start point • Work on deliverables • Test/refine • Launch
  8. 8. WE INVOLVE OUR CLIENTS AND STAKEHOLDERS • Discovery • Scope • Clarification • Testing • Demos • Training
  9. 9. BUT WHAT ELSE CAN WE DO?
  10. 10. POST- LAUNCH
  11. 11. WHAT PIECES OF CONTENT WILL GET UPDATED?
  12. 12. DOES THE CLIENT HAVE A TEAM IN PLACE TO UPDATE THE NEW SITE?
  13. 13. WHO ELSE IS INVOLVED IN MAINTENANCE DECISIONS?
  14. 14. WHAT DOES THE CONTENT PROCESS LOOK LIKE? From decision to content creation to approval to posting.
  15. 15. IS THERE A DESIGN/ DEVELOPMENT PLAN IN PLACE?
  16. 16. WHAT ABOUT SECURITY, UPDATES, AND INFRASTRUCTURE SUPPORT?
  17. 17. SOME CLIENTS HAVE SOME OF THIS COVERED. MOST DON’T HAVE ALL.
  18. 18. WE CAN REVERSE ENGINEER OUR PROCESSES TO INCLUDE EDUCATION + EXPECTATIONS
  19. 19. PRE- PROJECT Activity
  20. 20. WHAT QUESTIONS MIGHT YOU ASK ABOUT SITE & CONTENT MANAGEMENT? Activity
  21. 21. THE IMPORTANCE OF DISCOVERY
  22. 22. SET EXPECTATIONS ABOUT POST- LAUNCH BY ASKING UP-FRONT
  23. 23. GET THE STAKEHOLDER TEAM ON BOARD WITH THEIR RESPONSIBILITIES AFTER LAUNCH
  24. 24. FROM DISCOVERY TO PROJECT PLANNING
  25. 25. GREAT PROCESSES ENCOURAGE POST-LAUNCH SUCCESS
  26. 26. CAPTURING CONTENT MANAGER WORKFLOWS HELPS US DESIGN & DEVELOP BETTER
  27. 27. CREATE A CONTENT WORKFLOW & RESPONSIBILITIES MAP
  28. 28. RACI MATRIX FOR POST- LAUNCH PLANNING
  29. 29. RACI = RESPONSIBLE ACCOUNTABLE CONSULTED INFORMED
  30. 30. RESPONSIBLE Who does the work to achieve the task?
  31. 31. ACCOUNTABLE Who is responsible for the correct and thorough completion of the task?
  32. 32. CONSULTED Who provides information for the project and communicates regarding the tasks/projects?
  33. 33. INFORMED Who needs to be informed of progress and is affected by the outcome of the tasks?
  34. 34. PRE-PLAN THE MAINTENANCE WORKFLOW Activity
  35. 35. GET CLIENTS THINKING ABOUT THEIR OWN PROCESS
  36. 36. MANAGE EXPECTATIONS ABOUT PROJECT USE CASES FROM THE START
  37. 37. SOME CAN BE EXTREMELY SIMPLE:
  38. 38. OR IT COULD BE MUCH MORE COMPLEX: csffct.co/RGfGOu
  39. 39. PRE- LAUNCH
  40. 40. GIVE CLIENTS THE TOOLS TO MANAGE THEIR SITES
  41. 41. HOW CAN WE ENSURE THEY’RE EDUCATED AND PREPARED?
  42. 42. “PHASE 2”
  43. 43. ITERATIVE PROCESSES
  44. 44. FEATURE DEVELOPMENT
  45. 45. UPDATES/ MAINTENANCE PACKAGES
  46. 46. TYPICAL “LIFESPAN” OF A WEBSITE
  47. 47. PROCESSES NEED FEEDBACK LOOPS
  48. 48. Planning —> Research —> Design —> Development —> Launch —> Maintenance
  49. 49. Planning —> Research —> Design —> Development —> Launch —> Maintenance
  50. 50. Planning —> Research —> Design —> Development —> Launch —> Maintenance
  51. 51. SETTING UP PROJECTS FOR POST-LAUNCH SUCCESS REQUIRES PLANNING
  52. 52. PRE-PROJECT QUESTIONS AND RESPONSIBILITY PLANNING
  53. 53. DURING THE PROJECT, CONTENT AND SITE MANAGEMENT WORKFLOWS MUST BE CONSIDERED
  54. 54. POST-LAUNCH EXPECTATION SETTING, TRAINING, AND UPKEEP
  55. 55. LEADS TO: MORE MANAGEABLE WEBSITES, MORE UPDATED CONTENT, HAPPIER USERS ON BACK AND FRONT END
  56. 56. THANK YOU! Natalie Semczuk @talkanatalka natalie@goodmerit.co goodmerit.co talkanatalka.com

×