-
Notifications
You must be signed in to change notification settings - Fork 21
/
schedule.json
717 lines (717 loc) · 61.3 KB
/
schedule.json
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
{
"timezone": "America/Los_Angeles",
"sessions": [
{
"day": "Monday 18th May",
"sessions": [
{
"start_time": "2015-05-18 09:00:00",
"topics": [],
"web_url": "http://lanyrd.com/2015/writethedocs/sdmxyz/",
"times": "9:00am\u00a0-\u00a09:15am",
"id": "sdmxyz",
"types": [],
"end_time_epoch": 1431965700,
"speakers": [
{
"bio": "<p>Maintainer of Read the Docs. Co-creator of Write the Docs. Hiked 800 miles of the PCT. Wanderer.</p>",
"web_url": "http://lanyrd.com/profile/ericholscher/",
"image_300": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/5a2d1d00002e2cb179197c30718568116b8c2a1d-e18d4f-s300.jpg",
"name": "Eric Holscher",
"elsewhere": [],
"role": "Maintainer of Read the Docs. Co-creator of Write the Docs. Hiked 800 miles of the PCT. Wanderer.",
"twitter": "@ericholscher",
"image_75": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/5a2d1d00002e2cb179197c30718568116b8c2a1d-e18d4f-s75.jpg",
"speaker_bio": ""
}
],
"title": "Introduction",
"event_id": "cchpzt",
"space": null,
"day": "Monday 18th May",
"end_time": "2015-05-18 09:15:00",
"other_url": null,
"start_time_epoch": 1431964800,
"abstract": ""
},
{
"start_time": "2015-05-18 09:15:00",
"topics": [],
"web_url": "http://lanyrd.com/2015/writethedocs/sdmwxm/",
"times": "9:15am\u00a0-\u00a010:00am",
"id": "sdmwxm",
"types": [],
"end_time_epoch": 1431968400,
"speakers": [
{
"bio": "<p>Author of "Word Up!" and "You Can Say That Again"</p>",
"web_url": "http://lanyrd.com/profile/marciarieferjohnston/",
"image_300": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/179776ceb0d27e110d9bd7c99cb82b1b7f539935-s300.jpeg",
"name": "Marcia Riefer Johnston",
"elsewhere": [
{
"url": "http://writing.rocks/"
},
{
"url": "https://plus.google.com/u/0/+MarciaRieferJohnston/posts"
}
],
"role": "Author of \"Word Up!\" and \"You Can Say That Again\"",
"twitter": "@MarciaRJohnston",
"image_75": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/179776ceb0d27e110d9bd7c99cb82b1b7f539935-s75.jpeg",
"speaker_bio": ""
}
],
"title": "Keynote: We Are All Abbott and Costello",
"event_id": "cchpzt",
"space": null,
"day": "Monday 18th May",
"end_time": "2015-05-18 10:00:00",
"other_url": null,
"start_time_epoch": 1431965700,
"abstract": "<p>Documentarians and technical writers have seen many changes in our professions in recent years, and there\u2019s no sign of change slowing down. One thing endures: the writer's goal of communicating to understanding. It\u2019s not as easy as it sounds. Because we are all Abbott and Costello.</p>"
},
{
"start_time": "2015-05-18 10:10:00",
"topics": [],
"web_url": "http://lanyrd.com/2015/writethedocs/sdmwxp/",
"times": "10:10am\u00a0-\u00a010:40am",
"id": "sdmwxp",
"types": [],
"end_time_epoch": 1431970800,
"speakers": [
{
"bio": "<p>Principal Member of Technical Staff at Salesforce</p>",
"web_url": "http://lanyrd.com/profile/arthur-louie/",
"image_300": "https://d3brtmsfoeeao4.cloudfront.net/img/icons/flatset/person-300x300.aae55363.png",
"name": "Arthur Louie",
"elsewhere": [],
"role": "Principal Member of Technical Staff at Salesforce",
"twitter": null,
"image_75": "https://d3brtmsfoeeao4.cloudfront.net/img/icons/flatset/person-75x75.dc1c8979.png",
"speaker_bio": ""
},
{
"bio": "<p>Staff Technical Writer at <a href=\"http://Salesforce.com\" rel=\"nofollow\">Salesforce.com</a></p>",
"web_url": "http://lanyrd.com/profile/jodybleyle/",
"image_300": "https://d3brtmsfoeeao4.cloudfront.net/img/icons/flatset/person-300x300.aae55363.png",
"name": "Jody Bleyle",
"elsewhere": [],
"role": "Staff Technical Writer at Salesforce.com",
"twitter": null,
"image_75": "https://m3-s.licdn.com/mpr/mprx/0_-HOmp125cAPyL33iK70jplyBclNt53AiKfoAplgLHN8Cs56_YaaCtAdIJ0qS66rf1IpK197B7rua",
"speaker_bio": ""
}
],
"title": "Writer, Meet Tester",
"event_id": "cchpzt",
"space": null,
"day": "Monday 18th May",
"end_time": "2015-05-18 10:40:00",
"other_url": null,
"start_time_epoch": 1431969000,
"abstract": "<p>A software tester can be a tech writer\u2019s best friend, and vice versa. Jody (writer) and Arthur (tester) work together on APIs at <a href=\"http://Salesforce.com\" rel=\"nofollow\">Salesforce.com</a>, and we\u2019ll talk about the tools and techniques we use to improve the quality of both our software and our documentation at the same time.<br>\nWhile our APIs are still in development, we gather feedback internally. We established an API design review board to approve every API change -- this made a huge difference in ensuring that we offer a consistent, easy-to-consume programmatic interface to our users. We also conduct regular \u201cdogfooding\u201d sessions in which users are provided with draft documentation and asked to find both doc and product bugs.<br>\nOur testers created an automated mechanism to alert us of any API changes in case anything slipped past the review board. It\u2019s proven to be invaluable for both doc and testing to keep up with the various teams who are building functionality into the API.<br>\nOnce our APIs are publicly available, we take pride in listening to our users in help forums, on Twitter, and through pilot programs. We\u2019ve clarified our documentation and added test cases numerous times based on customer pain points.</p>"
},
{
"start_time": "2015-05-18 11:00:00",
"topics": [],
"web_url": "http://lanyrd.com/2015/writethedocs/sdmwxx/",
"times": "11:00am\u00a0-\u00a011:30am",
"id": "sdmwxx",
"types": [],
"end_time_epoch": 1431973800,
"speakers": [
{
"bio": "<p>techwriter. music journalist. sometimes poet.</p>",
"web_url": "http://lanyrd.com/profile/moerex/",
"image_300": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/4050d2c8b193f2c2c83a0ae6f391eb2470494721-s300.jpeg",
"name": "Matt Ness",
"elsewhere": [],
"role": "techwriter. music journalist. sometimes poet.",
"twitter": "@moerex",
"image_75": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/4050d2c8b193f2c2c83a0ae6f391eb2470494721-s75.jpeg",
"speaker_bio": ""
}
],
"title": "Let\u2019s Tell a Story: Scenario-Based Documentation",
"event_id": "cchpzt",
"space": null,
"day": "Monday 18th May",
"end_time": "2015-05-18 11:30:00",
"other_url": null,
"start_time_epoch": 1431972000,
"abstract": "<p>To new users, complex software products can seem like dark woods on a stormy day. As tech writers, we often spend a lot of time talking about the overall shape of the forest and the variety of paths within it (conceptual docs), creating detailed catalogs of local tree species (reference docs), and providing step-by-step guides to things like \u201chow to cross a river\u201d or \u201chow to knock on a door\u201d (task-based docs).<br>\nBut none of that helps your customers when they just want to know how to get to Grandmother\u2019s house, without getting lost in the forest, falling into the river, and accidentally going to the other cabin in the woods, where the lycanthropic senior citizens live.<br>\nIn other words, your customers need a narrative. And maybe they need lots of them. When you\u2019re dealing with products that can be run and configured in a bewildering variety of ways, a single getting started manual might not do the trick. It\u2019s like giving people a Choose Your Own Adventure book and only allowing them to choose one path through to the end.<br>\nFor my talk I\u2019ll explain how we became aware of the need for better scenario-based documentation, and how we ended up building a prototype during a hack week project. Now we\u2019re on our way to creating a collection of short stories that show users how to string sets of features and procedures together to solve complex problems. We\u2019ll cover some of the things we\u2019ve learned along the way and offer best practices for those who want to tell a few stories of their own.<br>\nMatt Ness is a technical writer with over twenty years of experience at places like PeopleSoft, Oracle, and Intuit. He's currently a writer for Splunk, a leader in the machine data analytics sector.</p>"
},
{
"start_time": "2015-05-18 11:40:00",
"topics": [],
"web_url": "http://lanyrd.com/2015/writethedocs/sdmwxy/",
"times": "11:40am\u00a0-\u00a012:10pm",
"id": "sdmwxy",
"types": [],
"end_time_epoch": 1431976200,
"speakers": [
{
"bio": "<p>I make HTTP requests for a living</p>",
"web_url": "http://lanyrd.com/profile/ekrubnivek/",
"image_300": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/e4ecf7a7534b7913c3ec4be2513efb1e907260ed-s300.jpeg",
"name": "Kevin Burke",
"elsewhere": [],
"role": "I make HTTP requests for a living",
"twitter": "@ekrubnivek",
"image_75": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/e4ecf7a7534b7913c3ec4be2513efb1e907260ed-s75.jpeg",
"speaker_bio": ""
}
],
"title": "How to Write Documentation for People that Don't Read",
"event_id": "cchpzt",
"space": null,
"day": "Monday 18th May",
"end_time": "2015-05-18 12:10:00",
"other_url": null,
"start_time_epoch": 1431974400,
"abstract": "<p>It's 3AM, do you know where your users are? If people want to learn how to use your product, where are they looking for help? Are they on your site, and if they're on your site, are they finding the right page?<br>\nUsability researchers have known for decades that users don't read word by word - they scan for the content they want.<br>\nIf users can't make heads or tails of your documentation, they'll give up (a loss of revenue), remain ignorant of product features (another loss of revenue) or ask needless support questions (an increased cost).<br>\nIn this talk we'll examine the findability of your documentation, and the text on the pages in your documentation. We'll examine usability research into how users read, look at several ways your documentation is failing busy users, and the lessons I learned conducting user tests at Twilio. We'll learn more about how users find the answers they are looking for, and the importance of spreading clear writing across not just your documentation, but your headlines and error messages in your API.</p>"
},
{
"start_time": "2015-05-18 13:10:00",
"topics": [],
"web_url": "http://lanyrd.com/2015/writethedocs/sdmxzg/",
"times": "1:10pm\u00a0-\u00a01:40pm",
"id": "sdmxzg",
"types": [],
"end_time_epoch": 1431981600,
"speakers": [],
"title": "Lightning Talks",
"event_id": "cchpzt",
"space": null,
"day": "Monday 18th May",
"end_time": "2015-05-18 13:40:00",
"other_url": null,
"start_time_epoch": 1431979800,
"abstract": ""
},
{
"start_time": "2015-05-18 13:50:00",
"topics": [],
"web_url": "http://lanyrd.com/2015/writethedocs/sdmwxz/",
"times": "1:50pm\u00a0-\u00a02:20pm",
"id": "sdmwxz",
"types": [],
"end_time_epoch": 1431984000,
"speakers": [
{
"bio": "<p>I'm a developer at Mozilla.</p>",
"web_url": "http://lanyrd.com/profile/gkoberger/",
"image_300": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/02521fdbe94ab42144ecc9e21fd17578cf5b7ac9-s300.jpg",
"name": "Gregory Koberger",
"elsewhere": [],
"role": "I'm a developer at Mozilla.",
"twitter": "@gkoberger",
"image_75": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/02521fdbe94ab42144ecc9e21fd17578cf5b7ac9-s75.jpg",
"speaker_bio": ""
}
],
"title": "A Developers Approach to Documentation: From Passive to Dynamic",
"event_id": "cchpzt",
"space": null,
"day": "Monday 18th May",
"end_time": "2015-05-18 14:20:00",
"other_url": null,
"start_time_epoch": 1431982200,
"abstract": "<p>The era of O\u2019Reilly books is done, finito, kaput. With so much of the developer experience online, we know a great deal about each individual user and about the code we document. Why, then, do we documentarians persist in providing the same walls of text to each of our readers, especially when there are so many more personalized ways of describing technical tools and code?<br>\nThis talk addresses the move from passive to dynamic documentation. As code goes mainstream, more and more consumers of APIs and technical writing will be non-technical. Technical writing bears a responsibility to reduce the learning curve as much as possible for these readers, and it can do that by being much more intimate about its relationship with them.</p>"
},
{
"start_time": "2015-05-18 14:30:00",
"topics": [],
"web_url": "http://lanyrd.com/2015/writethedocs/sdmwyb/",
"times": "2:30pm\u00a0-\u00a03:00pm",
"id": "sdmwyb",
"types": [],
"end_time_epoch": 1431986400,
"speakers": [
{
"bio": "",
"web_url": null,
"image_300": "https://d3brtmsfoeeao4.cloudfront.net/img/icons/flatset/person-300x300.aae55363.png",
"name": "Emily Hoffmann",
"elsewhere": [],
"role": null,
"twitter": null,
"image_75": "https://d3brtmsfoeeao4.cloudfront.net/img/icons/flatset/person-75x75.dc1c8979.png",
"speaker_bio": ""
},
{
"bio": "",
"web_url": "http://lanyrd.com/profile/alromanb/",
"image_300": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/b6492804520332d1509491e1f73b47414f1864bc-s300.png",
"name": "Alfonso Roman",
"elsewhere": [],
"role": "",
"twitter": "@alromanb",
"image_75": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/b6492804520332d1509491e1f73b47414f1864bc-s75.png",
"speaker_bio": ""
}
],
"title": "A brief history of math writing: symbol, structure, and proof",
"event_id": "cchpzt",
"space": null,
"day": "Monday 18th May",
"end_time": "2015-05-18 15:00:00",
"other_url": null,
"start_time_epoch": 1431984600,
"abstract": "<p>A mathematical proof is a logically rigorous way of showing that something is true. It begins with a statement of the desired result and any assumptions that must be made. It guides the reader through a set of logical sequential steps, supported by figures to aid intuition or cross-references for prerequisite knowledge. It ends by declaring that the desired result has been achieved. At risk of insulting every mathematician who ever lived, in many ways a proof is not so different from a grand, abstract how-to document.<br>\nPerhaps surprisingly, for most of human history mathematical proofs and mathematics itself have been written in prose. Even those of us who cringe at the memory of high school algebra can agree that \u201c10x + y^2 = 3\u201d is more user-friendly than \u201cthe sum of an unknown quality multiplied by ten and another unknown quantity multiplied by itself is equal to three\u201d. The first part of this talk explores the development of mathematical writing, which can be divided into improvements in symbolic representation and improvements in structure. This discussion is partly inspired by Bret Victor\u2019s observation that the most influential breakthroughs in the history of mathematics were actually breakthroughs in \u201cUI design\u201d, for example the invention of arabic numerals (0, 1, 2, 3,...) as a replacement for clunky roman numerals (I, II, III, IV\u2026).<br>\nProofs and rigorous documentation empower their readers to greater understanding by never relying on authority or persuasion. A mathematical proof, unlike a scientific experiment or a souffle recipe, must show that the desired result is always achieved when the right steps are executed under the right conditions. Users of computer applications certainly expect documentation to live up to the same standards. The second part of this talk explores the concept of mathematical proof in more depth. We will look at how proofs are structured and use logic in a particular way to minimize ambiguity and maximize credibility, and how the writing process is itself a powerful tool to root out hidden assumptions and errors in thinking.</p>"
},
{
"start_time": "2015-05-18 15:30:00",
"topics": [],
"web_url": "http://lanyrd.com/2015/writethedocs/sdmwyc/",
"times": "3:30pm\u00a0-\u00a03:45pm",
"id": "sdmwyc",
"types": [],
"end_time_epoch": 1431989100,
"speakers": [
{
"bio": "<p>Content strategist, writer, project manager, and owner of Kaia Communications. My interests include psychology, nutrition, dogs, and rock 'n roll music.</p>",
"web_url": "http://lanyrd.com/profile/karenronning/",
"image_300": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/ed0d3d0c3464561ce7d9fce50166e143c06a35ec-s300.jpeg",
"name": "Karen Ronning-Hall",
"elsewhere": [],
"role": "Content strategist, writer, project manager, and owner of Kaia Communications. My interests include psychology, nutrition, dogs, and rock 'n roll music.",
"twitter": "@karenronning",
"image_75": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/ed0d3d0c3464561ce7d9fce50166e143c06a35ec-s75.jpeg",
"speaker_bio": ""
}
],
"title": "The Science of Creating Unforgettable Content",
"event_id": "cchpzt",
"space": null,
"day": "Monday 18th May",
"end_time": "2015-05-18 15:45:00",
"other_url": null,
"start_time_epoch": 1431988200,
"abstract": "<p>Companies spend big bucks developing content to attract and retain customers\u2014most of it, forgettable. In fact, according to some cognitive scientists, people remember only 10 percent of what you say. The other 90 percent is forgotten. To make matters worse, the 10 percent that people remember differs between members of your audience.<br>\nImagine the time and money we could all save if we knew how to control what our audiences remember about our content, if we could break through all of the distractions with content so compelling that our audiences couldn\u2019t ignore our message.<br>\nIn a blog that I wrote, I had the opportunity to interview Dr. Carmen Simon. A co-founder of Rexi Media, Dr. Simon holds doctorates in instructional technology and cognitive psychology. We explored how science could help us design memorable content.<br>\nIn my Write the Docs presentation, I\u2019ll share five scientifically-based techniques that the audience can apply to their own content and presentations to make them more memorable and influential. This presentation will be based on information from my interview with Dr. Simon and other sources.</p>"
},
{
"start_time": "2015-05-18 15:45:00",
"topics": [],
"web_url": "http://lanyrd.com/2015/writethedocs/sdmwyd/",
"times": "3:45pm\u00a0-\u00a04:00pm",
"id": "sdmwyd",
"types": [],
"end_time_epoch": 1431990000,
"speakers": [
{
"bio": "<p>Academy Engineer at OutSystems, learner of all things.</p>",
"web_url": "http://lanyrd.com/profile/joaofnfernandes/",
"image_300": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/579e015e3d4c031b4eef2a6a66ca4f7b20e689c3-s300.jpeg",
"name": "Joao Fernandes",
"elsewhere": [],
"role": "Academy Engineer at OutSystems, learner of all things.",
"twitter": "@joaofnfernandes",
"image_75": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/579e015e3d4c031b4eef2a6a66ca4f7b20e689c3-s75.jpeg",
"speaker_bio": ""
}
],
"title": "User-Story Driven Docs",
"event_id": "cchpzt",
"space": null,
"day": "Monday 18th May",
"end_time": "2015-05-18 16:00:00",
"other_url": null,
"start_time_epoch": 1431989100,
"abstract": "<p>At OutSystems we make an awesome development platform, but our documentation wasn't that awesome. We focused on describing each button available on the user interface, and not the user intentions and goals.<br>\nA clear example of this, was that we had a full documentation page for the find text feature (CTRL+F). It described in excruciating detail every option available on the UI, but didn't told our users how they could actually find what they needed!<br>\nFor us it was a nightmare to maintain the docs. Our development environment was constantly changing and we couldn't keep up with the changes.<br>\nMore importantly, we weren't meeting the user needs. And that was clear from pages with a single-digit page view, and from the feedback we got from our customers.<br>\nDue to this approach, we also ended up having page titles that were feature-oriented, which is not the best for SEO. For instance, the doc page for the find text feature was called "Find Tool". Who in their right mind would search for that on Google?<br>\nIn this talk I'll tell you the story of how we stopped trying to document the UI, and started creating user-story driven docs. We now focus on what the user wants to achieve and how to achieve it, independently of how many windows or buttons they need to go through.<br>\nI'll cover:<br>\nHow you can check if you're documenting the UI, and why you should avoid doing it<br>\nWhy users stories work better for our users<br>\nHow focusing on user stories changed the culture of our team and allowed us to work on what really matters.<br>\nI'll also share some unexpected outcomes, like how this lead us to work closer than ever with the development teams. Now our users get twice the cake: better features and better docs!</p>"
},
{
"start_time": "2015-05-18 16:10:00",
"topics": [],
"web_url": "http://lanyrd.com/2015/writethedocs/sdmwyg/",
"times": "4:10pm\u00a0-\u00a04:40pm",
"id": "sdmwyg",
"types": [],
"end_time_epoch": 1431992400,
"speakers": [
{
"bio": "<p>Documentation Lead at Jive Software</p>",
"web_url": "http://lanyrd.com/profile/marya-devoto/",
"image_300": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/9fd0624d2aa1c12d53835b6c2c1ae5dfc31eaea0-s300.jpeg",
"name": "Marya DeVoto",
"elsewhere": [],
"role": "Documentation Lead at Jive Software",
"twitter": null,
"image_75": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/9fd0624d2aa1c12d53835b6c2c1ae5dfc31eaea0-s75.jpeg",
"speaker_bio": ""
}
],
"title": "Designing Information for Growth",
"event_id": "cchpzt",
"space": null,
"day": "Monday 18th May",
"end_time": "2015-05-18 16:40:00",
"other_url": null,
"start_time_epoch": 1431990600,
"abstract": "<p>Every tech company or organization organically produces docs in some form, but as scale increases, the information design decisions you started with will almost certainly serve some information consumers better than others. Depending on who's creating information and who's using it, the approach to designing and delivering information can be dramatically different, with very different outcomes that probably won't work across an entire larger organization. Be aware of the information design decisions you're making so you can plan for growth. Design by default is not a good strategy!<br>\nThis talk discusses how:<br>\nInformation inherently includes design, whether or not you meant to do it. Information also requires design, no matter how simple and straightforward it may seem.<br>\nTechnical information can be roughly sorted into modes such as descriptive, defensive, procedural, and tutorial. (These are different from concept-task-reference.)<br>\nEach of these modes has different design implications that address different audiences and needs.<br>\nBeing aware of your design priorities can help you understand how to make your stakeholders happier as your documentation base grows with the organization.</p>"
},
{
"start_time": "2015-05-18 16:50:00",
"topics": [],
"web_url": "http://lanyrd.com/2015/writethedocs/sdmwyf/",
"times": "4:50pm\u00a0-\u00a05:20pm",
"id": "sdmwyf",
"types": [],
"end_time_epoch": 1431994800,
"speakers": [
{
"bio": "<p>Lead technical writer at Atlassian</p>",
"web_url": "http://lanyrd.com/profile/christine-burwinkle/",
"image_300": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/fb2b06ba771712206e70b46467335d1ee404deac-s300.jpeg",
"name": "Christine Burwinkle",
"elsewhere": [],
"role": "Lead technical writer at Atlassian",
"twitter": null,
"image_75": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/fb2b06ba771712206e70b46467335d1ee404deac-s75.jpeg",
"speaker_bio": ""
}
],
"title": "Tech writing in a continuous deployment world",
"event_id": "cchpzt",
"space": null,
"day": "Monday 18th May",
"end_time": "2015-05-18 17:20:00",
"other_url": null,
"start_time_epoch": 1431993000,
"abstract": "<p>Here at Atlassian, we\u2019ve been moving ever closer to a world of continuous deployment for our software products. Five years ago, releases took months. Now, many products are releasing every two weeks at a minimum. In addition, the past year has seen features being deployed as soon as they pass testing. What\u2019s a tech writer to do!?<br>\nIn true agile fashion, the response to these challenges varies across products and writers within Atlassian. This gives us a breadth of stories and examples I can share about our experiences in this world. Here\u2019s a high-level look at what I\u2019ll share:<br>\nA brief discussion of continuous deployment: what does it mean, especially for tech writers and others involved in the process?<br>\nA look at some things that have worked for us. Making the mental shift from releases to features has been an absolute necessity. We\u2019ve also had to change the tooling we use, the processes we follow, and the way we communicate. This journey has also forced us to consider what the documentation equivalent of an MVP (minimal viable product in Agile development) looks like.<br>\nThere are a few things that haven\u2019t worked out very well! Resource-heavy deliverables (like videos and tutorials) are really difficult to maintain. Communication also increases in importance in a rapidly-paced cycle. These and other areas provide us with some good lessons learned.<br>\nThe jury is still out on a few experiments! Things like investing more heavily in in-app help and automating doc publication in tandem with code deployment are among the experiments we\u2019re attempting to get better at this new world.</p>"
}
]
},
{
"day": "Tuesday 19th May",
"sessions": [
{
"start_time": "2015-05-19 09:15:00",
"topics": [],
"web_url": "http://lanyrd.com/2015/writethedocs/sdmwxk/",
"times": "9:15am\u00a0-\u00a010:00am",
"id": "sdmwxk",
"types": [],
"end_time_epoch": 1432054800,
"speakers": [
{
"bio": "<p>Objects, Patterns, Agile, Wiki</p>",
"web_url": "http://lanyrd.com/profile/wardcunningham/",
"image_300": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/ac6023130b9ff1d26cae601d9dd7a0faadf24786-s300.jpg",
"name": "Ward Cunningham",
"elsewhere": [],
"role": "Objects, Patterns, Agile, Wiki",
"twitter": "@WardCunningham",
"image_75": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/ac6023130b9ff1d26cae601d9dd7a0faadf24786-s75.jpg",
"speaker_bio": ""
}
],
"title": "Keynote: The Federated Wiki",
"event_id": "cchpzt",
"space": null,
"day": "Tuesday 19th May",
"end_time": "2015-05-19 10:00:00",
"other_url": null,
"start_time_epoch": 1432052100,
"abstract": "<p>Just as the first wiki changed how people write, our new wiki will change how people work. By pushing steadily on two fundamental ideas, refactoring to ease improvement and federation to ease sharing, we have once again uncovered a simpler and more powerful internet.</p>"
},
{
"start_time": "2015-05-19 10:10:00",
"topics": [],
"web_url": "http://lanyrd.com/2015/writethedocs/sdmwxh/",
"times": "10:10am\u00a0-\u00a010:40am",
"id": "sdmwxh",
"types": [],
"end_time_epoch": 1432057200,
"speakers": [
{
"bio": "<p>Mozilla community manager for developer documentation. Superpower: taking things literally</p>",
"web_url": "http://lanyrd.com/profile/jmswisher/",
"image_300": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/0f0d512b8005698404bdbb6b86435145058c7708-s300.jpeg",
"name": "Janet Swisher",
"elsewhere": [],
"role": "Mozilla community manager for developer documentation. Superpower: taking things literally",
"twitter": "@jmswisher",
"image_75": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/0f0d512b8005698404bdbb6b86435145058c7708-s75.jpeg",
"speaker_bio": ""
}
],
"title": "Entry points and guide posts: Helping new contributors find their way",
"event_id": "cchpzt",
"space": null,
"day": "Tuesday 19th May",
"end_time": "2015-05-19 10:40:00",
"other_url": null,
"start_time_epoch": 1432055400,
"abstract": "<p>How did Mozilla Developer Network (MDN) achieve a 46% increase in active editors and a 90% increase in translation contributions in 2014? Many factors helped, but a major element was the support we added for new contributors.<br>\n\u201cScratch your own itch\u201d is the proverbial invitation to contribute to open source projects. How well this works for contributing to code is open to debate, but it rarely makes sense for open source documentation, especially for well-established projects. Not only is it unhelpful for the project, which typically has plans (or at least wishlists) for improving the docs, but it provides very little guidance to the contributor as to what they might do, what they personally are able to do, and what would be most helpful to do.<br>\nIn the 10 years that MDN has been a wiki (some of the content pre-dates the wiki), the community has always welcomed constructive contributions by anyone who bothers to create a user account. Over the years, we\u2019ve created meta-documentation about contributing to the site, including wishlists of things we\u2019d like to see documented. However, these didn\u2019t necessarily help newcomers gain traction.<br>\nOnly in the last year or so have we created documentation to help new contributors specifically. Our aim is to help newcomers find the right match among:<br>\nTopics and tasks the person is interested in (what they like)<br>\nTasks the person has the skills and time to do (what they can do)<br>\nTasks that help MDN meet the goals that Mozilla has set (what we need/want)<br>\nI\u2019ll describe the features we\u2019ve put in place to achieve this, as well as things we\u2019re still working on. I\u2019ll leave space for discussion so we can all share ideas and successes.</p>"
},
{
"start_time": "2015-05-19 11:00:00",
"topics": [],
"web_url": "http://lanyrd.com/2015/writethedocs/sdmwxg/",
"times": "11:00am\u00a0-\u00a011:30am",
"id": "sdmwxg",
"types": [],
"end_time_epoch": 1432060200,
"speakers": [
{
"bio": "<p>unreliable narrator</p>",
"web_url": "http://lanyrd.com/profile/rionam/",
"image_300": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/7003128a8651a91125ecd5baa86e4395dd0421f2-s300.jpg",
"name": "Riona MacNamara",
"elsewhere": [],
"role": "unreliable narrator",
"twitter": "@rionam",
"image_75": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/7003128a8651a91125ecd5baa86e4395dd0421f2-s75.jpg",
"speaker_bio": ""
}
],
"title": "Documentation, Disrupted: How Two Technical Writers Changed Google Engineering Culture",
"event_id": "cchpzt",
"space": null,
"day": "Tuesday 19th May",
"end_time": "2015-05-19 11:30:00",
"other_url": null,
"start_time_epoch": 1432058400,
"abstract": "<p>Last year, we were inspired to action by a presentation at Write the Docs. This talk will tell the story of what happened next: how, in two quarters, we worked with a small self-forming team of amazing writers and engineers to build a platform in six months is well on the way to becoming a part of the standard Google engineering workflow. We\u2019ll share how that platform transformed our role as technical writers and our relationship with engineering. We\u2019ll cover design and implementation details, but we\u2019ll also talk about our experience - how we learned that being audacious (but not reckless), focused (but open and generous), and unafraid could revitalize our whole approach to work and save us from burnout.<br>\nWe'll talk about our ever-growing appetite for disruption: How it changed beyond recognition our relationships with engineers, fellow writers, and senior leadership, making us fall in love again with our roles as documentarians.</p>"
},
{
"start_time": "2015-05-19 11:40:00",
"topics": [],
"web_url": "http://lanyrd.com/2015/writethedocs/sdmwxf/",
"times": "11:40am\u00a0-\u00a012:10pm",
"id": "sdmwxf",
"types": [],
"end_time_epoch": 1432062600,
"speakers": [
{
"bio": "<p>'Ukulele-playing, hula-dancing, telecommuting Agile team member specializing in technical communications, user assistance, and QA. Passionate about all of it.</p>",
"web_url": "http://lanyrd.com/profile/tanafranko/",
"image_300": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/0aab669d28055bdd3f612d2a22ee608f327e8d49-s300.jpeg",
"name": "Tana Franko",
"elsewhere": [],
"role": "'Ukulele-playing, hula-dancing, telecommuting Agile team member specializing in technical communications, user assistance, and QA. Passionate about all of it.",
"twitter": "@tanafranko",
"image_75": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/0aab669d28055bdd3f612d2a22ee608f327e8d49-s75.jpeg",
"speaker_bio": ""
}
],
"title": "Elevating the Hedgehog: Creativity in Tech Writing",
"event_id": "cchpzt",
"space": null,
"day": "Tuesday 19th May",
"end_time": "2015-05-19 12:10:00",
"other_url": null,
"start_time_epoch": 1432060800,
"abstract": "<p>"People who hope to thrive in the Conceptual Age must understand the connections between diverse, and seemingly separate, disciplines." So says Daniel Pink in his book, A Whole New Mind: Why Right-Brainers Will Rule the Future. In this talk, I assert that tech writers are a natural fit to help their organizations transition from the Information Age to the Conceptual Age. I'll also give and seek ideas on how we as writers can apply Pink's six aptitudes -- storytelling, empathy, design, humor, games, and finding meaning -- to make our work more fulfilling, if not more competitive.<br>\nThe key underlying message for those who attend this talk is: YOU are a designer. Even if you haven't traditionally seen yourself in this role, writers are information designers who serve a unique, user-focused and holistic function on development teams. By recognizing that fact, and opening up space in your work life for creativity, you can have an even bigger impact and a more fulfilling career.</p>"
},
{
"start_time": "2015-05-19 13:10:00",
"topics": [],
"web_url": "http://lanyrd.com/2015/writethedocs/sdmxzh/",
"times": "1:10pm\u00a0-\u00a01:40pm",
"id": "sdmxzh",
"types": [],
"end_time_epoch": 1432068000,
"speakers": [],
"title": "Lightning Talks",
"event_id": "cchpzt",
"space": null,
"day": "Tuesday 19th May",
"end_time": "2015-05-19 13:40:00",
"other_url": null,
"start_time_epoch": 1432066200,
"abstract": ""
},
{
"start_time": "2015-05-19 13:50:00",
"topics": [],
"web_url": "http://lanyrd.com/2015/writethedocs/sdmwxd/",
"times": "1:50pm\u00a0-\u00a02:20pm",
"id": "sdmwxd",
"types": [],
"end_time_epoch": 1432070400,
"speakers": [
{
"bio": "<p>Le Henne de Meaux: what's *really* on his mind</p>",
"web_url": "http://lanyrd.com/profile/synthcat/",
"image_300": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/5401dff292153c837e3adbcf1a09297be7fc3c65-s300.jpeg",
"name": "Mo Nishiyama",
"elsewhere": [],
"role": "Le Henne de Meaux: what's *really* on his mind",
"twitter": "@synthcat",
"image_75": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/5401dff292153c837e3adbcf1a09297be7fc3c65-s75.jpeg",
"speaker_bio": ""
}
],
"title": "What Can Brownfield Do For You?",
"event_id": "cchpzt",
"space": null,
"day": "Tuesday 19th May",
"end_time": "2015-05-19 14:20:00",
"other_url": null,
"start_time_epoch": 1432068600,
"abstract": "<p>As documentarians, we are rarely afforded an opportunity to thrive in a pristine greenfield environment. Sometimes we are asked to resurrect an existing documentation system which had fallen into a derelict state over many years. To turn this ship around, we must shepherd contents, customer base, and internal Subject Matter Experts into a future state where outdated, neglected, and ambiguous support documents are transformed into timely, relevant, and pleasing works of art.<br>\nThe role of the documentarian is to help execute this transformation. However, we are often asked (or voluntold) by our organizations to wear other hats beyond our primary writing duties: repair and build relationships, analyze business processes, learn about how others react to change, discover unknown troves of documentation, train and encourage the next generation of writers, gather and crunch data, tell stories, design workflows, and perform \u201cother duties as needed.\u201d Some may respond with an exasperated \u201cI wasn\u2019t trained on this!!!\u201d or \u201cThat\u2019s not part of my job!\u201d But those of us who embrace the opportunity to stretch beyond our areas of expertise and learn new peripheral skills may realize that working on a documentation equivalent of a cleaning up Superfund site can turn into super fun.<br>\nIn this talk, I will share my experiences and lessons learned as a technical writer who is witnessing this documentation culture change, one conversation at a time. Wearing many hats can be exhilarating and rewarding.</p>"
},
{
"start_time": "2015-05-19 14:30:00",
"topics": [],
"web_url": "http://lanyrd.com/2015/writethedocs/sdmwxc/",
"times": "2:30pm\u00a0-\u00a03:00pm",
"id": "sdmwxc",
"types": [],
"end_time_epoch": 1432072800,
"speakers": [
{
"bio": "<p>I inhale and exhale.</p>",
"web_url": "http://lanyrd.com/profile/gjtorikian/",
"image_300": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/cff0822e88f64a5b45dd0cebe21ba4ef94f89433-s300.jpeg",
"name": "Garen J. Torikian",
"elsewhere": [],
"role": "I inhale and exhale.",
"twitter": "@gjtorikian",
"image_75": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/cff0822e88f64a5b45dd0cebe21ba4ef94f89433-s75.jpeg",
"speaker_bio": ""
}
],
"title": "How GitHub uses GitHub to document GitHub",
"event_id": "cchpzt",
"space": null,
"day": "Tuesday 19th May",
"end_time": "2015-05-19 15:00:00",
"other_url": null,
"start_time_epoch": 1432071000,
"abstract": "<p>Everyone knows that GitHub is the place to host your project's code. What you may not know is that the same workflow developers use to create, update, and manage their software is also used to create, update, and manage GitHub's documentation.<br>\n<a href=\"https://help.github.com\" rel=\"nofollow\">https://help.github.com</a> is GitHub's second-most viewed site--after the main website itself. I'd like to provide a somewhat opinionated look on how our valiant Documentation team writes and releases content for features on <a href=\"http://GitHub.com\" rel=\"nofollow\">GitHub.com</a> and GitHub Enterprise. I'll go over:<br>\nHow our teams (Development, Security, Docs, etc) coordinate before launching a feature<br>\nThe importance of opening pull requests early<br>\nThe review/edit cycle with peers<br>\nHow we incorporate DITA best practices into our Markdown documentation<br>\nValidating content through CI and automated tests<br>\nHow we incorporate feedback from our users</p>"
},
{
"start_time": "2015-05-19 15:30:00",
"topics": [],
"web_url": "http://lanyrd.com/2015/writethedocs/sdmwwz/",
"times": "3:30pm\u00a0-\u00a03:45pm",
"id": "sdmwwz",
"types": [],
"end_time_epoch": 1432075500,
"speakers": [
{
"bio": "<p>Pied Piper of documentation and translator of Geek @Fastly. Self-proclaimed miracle worker.</p>",
"web_url": "http://lanyrd.com/profile/gwalli/",
"image_300": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/f8d469e812de8d712e6b5574d294183779e67bdf-s300.jpeg",
"name": "Gaylin Walli",
"elsewhere": [],
"role": "Pied Piper of documentation and translator of Geek @Fastly. Self-proclaimed miracle worker.",
"twitter": "@gwalli",
"image_75": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/f8d469e812de8d712e6b5574d294183779e67bdf-s75.jpeg",
"speaker_bio": ""
}
],
"title": "The Making of Writing Black Belts: How Martial Arts Philosophy Forged an Ad-Hoc Writing Team that Writes Great Docs",
"event_id": "cchpzt",
"space": null,
"day": "Tuesday 19th May",
"end_time": "2015-05-19 15:45:00",
"other_url": null,
"start_time_epoch": 1432074600,
"abstract": "<p>At Fastly, a San Francisco-based content delivery network startup company, I\u2019ve learned that almost every one of my co-workers, regardless of their job function, is willing to write our company\u2019s documentation. Whether they realize it or not, each one of them has ventured onto the path of becoming a \u201cwriting team black belt.\u201d<br>\nIn this talk I\u2019ll discuss how my company has unwittingly followed the seven (and a half) rules I normally associate with becoming a great martial artist. I\u2019ll discuss how we\u2019ve been using these rules to forge an amazing ad-hoc documentation team with no formal department and no squad of strategically placed technical writers. I\u2019ll talk about how my company has managed it despite the obstacles of startup life, including moving seven times and growing from less than 30 employees when I first joined to a throng of more than 150 a mere year and a half later. Finally, I\u2019ll point out some of our successes, a few of our failures, and how each of the seven (and a half) rules has taught us what it means to write Fastly.</p>"
},
{
"start_time": "2015-05-19 15:45:00",
"topics": [],
"web_url": "http://lanyrd.com/2015/writethedocs/sdmwwy/",
"times": "3:45pm\u00a0-\u00a04:00pm",
"id": "sdmwwy",
"types": [],
"end_time_epoch": 1432076400,
"speakers": [
{
"bio": "",
"web_url": "http://lanyrd.com/profile/michaeljang-2588/",
"image_300": "https://d3brtmsfoeeao4.cloudfront.net/img/icons/flatset/person-300x300.aae55363.png",
"name": "Mike Jang",
"elsewhere": [],
"role": "Senior Technical Writer, ForgeRock",
"twitter": null,
"image_75": "https://d3brtmsfoeeao4.cloudfront.net/img/icons/flatset/person-75x75.dc1c8979.png",
"speaker_bio": ""
}
],
"title": "Start Your Own Write The Docs Meetup Group",
"event_id": "cchpzt",
"space": null,
"day": "Tuesday 19th May",
"end_time": "2015-05-19 16:00:00",
"other_url": null,
"start_time_epoch": 1432075500,
"abstract": "<p>With just a little work, you can feel the joy of Write The Docs all year!<br>\nI started the Write The Docs PDX Meetup Group back in May of 2014, just after last year\u2019s conference. As the only writer in my office, I often feel alone. At Write The Docs NA 2014 conference, I felt the joy of interacting with documentarians like myself, people who were facing similar challenges. I wanted to continue feeling that joy.<br>\nI\u2019ll describe my experiences creating a Write The Docs Meetup group in Portland. I\u2019ll show you how easy* it is to create a Meetup group, attract members, get sponsors, find speakers, and make sure all members of your group feel welcome. I\u2019ll tell you about the Meetups we\u2019ve had, and what we learned from each other.<br>\nMore importantly, I\u2019ll lay out the ways you can continue the conversation we've had during WTD 2015. I'll share my best practices for excellent Meetups for Documentarians.<br>\n*Yes, \u201ceasy\u201d is a euphemism for a lot of hard work. But the people you'll meet and the contacts that you'll make can reward you and your company in other ways.</p>"
},
{
"start_time": "2015-05-19 16:10:00",
"topics": [],
"web_url": "http://lanyrd.com/2015/writethedocs/sdmwwx/",
"times": "4:10pm\u00a0-\u00a04:40pm",
"id": "sdmwwx",
"types": [],
"end_time_epoch": 1432078800,
"speakers": [
{
"bio": "<p>SF/F author, Microsoft/Xbox technical writer, and former science teacher. I tell the truth, sometimes with fiction.</p>",
"web_url": "http://lanyrd.com/profile/torreybird/",
"image_300": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/965426d5e2b21721a66a333fca55f9ba01fde87e-s300.jpeg",
"name": "Torrey Podmajersky",
"elsewhere": [],
"role": "SF/F author, Microsoft/Xbox technical writer, and former science teacher. I tell the truth, sometimes with fiction.",
"twitter": "@torreybird",
"image_75": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/965426d5e2b21721a66a333fca55f9ba01fde87e-s75.jpeg",
"speaker_bio": ""
}
],
"title": "Keep 'em playing",
"event_id": "cchpzt",
"space": null,
"day": "Tuesday 19th May",
"end_time": "2015-05-19 16:40:00",
"other_url": null,
"start_time_epoch": 1432077000,
"abstract": "<p>When people have to stop to understand labels and instructions, they can't stay engaged in their experiences. My job shipping Xbox One was to use words so well, people wouldn't notice them at all. In this talk, I'll show the only 3 reasons I use words in user interfaces, how I find the right words, and how I increase engagement by respecting people\u2019 intent.</p>"
},
{
"start_time": "2015-05-19 16:50:00",
"topics": [],
"web_url": "http://lanyrd.com/2015/writethedocs/sdmpdt/",
"times": "4:50pm\u00a0-\u00a05:20pm",
"id": "sdmpdt",
"types": [],
"end_time_epoch": 1432081200,
"speakers": [
{
"bio": "<p>Explaininator.</p>",
"web_url": "http://lanyrd.com/profile/wiredferret/",
"image_300": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/420db7434051045d9cc0e98e742c6121795693b3-s300.jpeg",
"name": "Heidi Waterhouse",
"elsewhere": [
{
"url": "https://www.linkedin.com/in/heidiwaterhouse/"
},
{
"url": "https://prezi.com/user/hwaterhouse/"
}
],
"role": "Explaininator.",
"twitter": "@wiredferret",
"image_75": "https://d8142femxnlg1.cloudfront.net/cropped-profile-photos/420db7434051045d9cc0e98e742c6121795693b3-s75.jpeg",
"speaker_bio": ""
}
],
"title": "Success is more than not-failing",
"event_id": "cchpzt",
"space": null,
"day": "Tuesday 19th May",
"end_time": "2015-05-19 17:20:00",
"other_url": null,
"start_time_epoch": 1432079400,
"abstract": "<p>We talk a lot about minimum viable products, and building our products up from small features. We talk a lot about failure, and how to learn from it and not replicate failures over and over again. But what I haven\u2019t heard a lot of discussion about is how we know we\u2019ve succeeded. Is it market share? Usable product? Could understanding and setting a measurable, achievable goals help us overcome imposter syndrome, second sock syndrome, and feature creep?<br>\nThis talk provides some metrics on identifying success, documenting what it will look like when you get there, preserving the idea, and dealing with the inevitable distractions and changes in direction that may prevent you from ending up where you expect.<br>\nI plan to speak on how documentation can serve a crucial function at both defining and driving success. We need to stop believing that agile is the end of the answer and embrace it as part of building what we want to have in the end.<br>\nContinuous improvement can have a victory condition, if we build it.</p>"
}
]
}
]
}