3. Ooops...
• No plan
• No structure
• No timeline
• No support
• No budget
4. Hmmm...
• We had experience
• We had motivation
• We had passion
• We had determination
• We made time
5. Cool USPs...
• Martin’s 1st hand experience
• Michael’s on the ground
understanding
• Jon’s SAP Ed expertise
• Den’s part baked vision
• Leo’s balance
7. Early decisions
• Do not use SAP Wiki
• Everyone has a voice
• Finagle the voices into
something coherent
• Use quasi SCRUM
• Limit the work
• Be respectful at all times
8. Step 1
• Went away and thought
• Came back with
individual rough cuts
• Elected DAH to edit with
help from Jon
• Michael/Jon formatting
9. Step 2
• Attend SAP Ed webinar
• Refine paper
• Present to SAP Ed for
comments
• Present to Mentors
• More refining (watch time
limit re: SAPPHIRE)
10. Step 3
• Publish and duck
• Start marketing
• Make noise
• Block and tackle
11. Marketing
• Present to Mentors (webinar)
• SDN post
• Twitter pimping (@certification5/
@C5)
• LinkedIn, Facebook, other posts
• The cartoon
• SAPPHIRE 2010
• Hats
• eGeeks/FMR
12. What worked
• Early drafts in good shape
• Tracking changes in GDocs
(but not recommended)
• Keeping to time on calls
• Being honest about
availability = expectations
met
• Making it fun
13. What didn’t work
• SAP collaboration was
largely one sided
• Under estimated SAP
issues
• Inadequate thought about
post-launch activities