11
Where No Wiki Has Gone Before
2
•Nick Smith• Information Manager
2
33
Where No Wiki Has Gone Before
4
•Nick Smith• Information Manager
4
55
66
7
Ares Preliminary
Design Review (PDR)
7
8
Importance
• Rigorous
• Funding
• Safety
8
9
People
9
10
People
10
11
People
11
12
People
12
13
People
13
14
People
14
15
People
15
16
Data
• ~75 documents, 2 weeks
• Logistical information
• Diverse review team
16
17
Challenges
• Coordination
• Technical bottlenecks
• Lots of changes
17
18
Our Role
• Not System Administrators
• Space Admins
18
Our Solution
19
Design Train Tweak
19
2020
21
• Surveys
• Overwhelmingly positive
• Huge success
Results
21
Top Ten Things We Learned
•10. Avoid chaos.
•9. A wiki is just a tool.
•8. Trust is the most important thing in a wiki.
•7. Empower the user.
•6. Put wikis in their terms.
22
•5. Tutor your users.
•4. Every team needs a fluent wiki whisperer.
•3. ???
•2. ???
•1. ???
22
#3Get away from the computer.
2323
Go talk to people.
2424
25
If you have the ideas you can do a lot without machinery. Once you have those ideas, the machinery starts working for you...
Most ideas you can do pretty darn well with a stick in the sand.
Alan Kay, American computer scientist
“25
Make a plan.
2626
2727
28
Header
Footer
28
2929
3030
31
#3Get away from the computer.
31
32
#2Shoot for Star Wars.
32
3333
3434
3535
3636
Great wikis balancestory and spectacle.
3737
38
#2Shoot for Star Wars.
38
#1KISS Confluence.
3939
4040
4141
4242
4343
4444
4545
4646
4747
4848
People like simple tools.
4949
50
People like simple tools.use
50
51
#1KISS Confluence.
#2Shoot for Star Wars.
#3Get away from the computer.
51
Questions?Why did you have to train your users?
Arenʼt wikis, by nature, unplanned/spontaneous?
If a wiki has to be designed, doesnʼt that mean itʼs already too complex?
5252
53Slide Credit: Garr Reynolds Image Credit: Ryota Mori
Jake Shimabukuro
53
54
Website: freedomis.comBlogs: blogs.freedomis.com
Twitter: @freedomis
Nick [email protected]
Twiter: @nsmithfreedom
54
Recommended
