All my sketchnotes from AotB 2016:
All my sketchnotes from AotB 2016:
[English summary: We wrote a book at work (in German) and it turned out amazing!!! It’s a cross between coffee table and business book. Watch out for “24 Work Hacks“! If you’d be interested in an English version, tell me so that I can make a case for translating it 🙂 ]
Endlich, endlich, darf ich es offiziell verkünden: Wir haben auf der Arbeit (ich arbeite bei sipgate) ein Buch geschrieben und es ist fantastisch geworden! Eine einzigartige Mischung aus Business- und CoffeeTable-Buch, d.h. richtig gute Fotos plus knackige Texte.
Wir haben versucht einen Rundgang durch unser Büro in Buchform zu gießen. Im Herbst 2015 haben wir mit Touren angefangen und seitdem Tausende Besucher herumgeführt und ihnen von unserer Arbeitsweise erzählt. Die Themen reichen von agilen Klassikern wie Retrospektiven bis zu innovativen, eigenen Lösungen wie Open Friday, Peer Feedback und vielem mehr.
Die bisherigen Rückmeldungen zu Beta-Versionen des Buchs bestätigen uns, dass “24 Work Hacks” richtig Lust darauf macht, agil und lean zu arbeiten. Ich wünschte, das Buch hätte es gegeben, als wir 2010 mit Scrum anfingen, denn wir hatten damals keine Ahnung, wie das alles aussehen könnte, wenn wir’s durchziehen. Naja, es hat auch so geklappt, aber leicht war’s nicht und die Inspiration und Vision im Buch hätte uns sicher geholfen.
“24 Work Hacks” erscheint am 15. September. Ihr könnt gerne schon mal auf Amazon vorbestellen 🙂
Mehr Infos, Bilder, ein Kapitel zum Probelesen usw. findet ihr auf der offiziellen Website zu “24 Work Hacks“.
Oh wow, where do I even start? “Badass – Making Users Awesome” by Kathy Sierra is a truly enlightening read. It contains ideas I’ve never heard before in the very accessible style of the “Head First” books. Sierra makes the case that in order to build a great product and a loyal customer base you have to make your users better in the use of the domain your product is in. If you make a marketing tool, make your users better marketers. IDE? Help them advance their coding craft.
Towards that end she devotes about half the book to explain how humans acquire skills and become experts. I got so carried away that I condensed it into a Wall-Skills 1-pagers. But it can’t possibly do justice to the book, so read it. It’s very insightful!
[English summary: Popular podcaster Toby Baier and me talk about the Product Owner during the initial transition / adoption / ignition / <find a better word> to Scrum in his podcast series “Agiles Produktmanagement”.]
Die POs unter euch kennen wahrscheinlich schon Toby Baiers Podcast “Agiles Produktmanagement”. In Folge 14 unterhält sich Toby mit mir über den “Product Owner in der agilen Transition”. Dem geht ein Exkurs über die Unzulänglichkeiten des Wortes “Transition” voraus 🙂
Die Folge bekommt ihr hier. Viel Spaß beim Hören!
[English summary: I’ve translated my experience reports about regular, company-wide Open Spaces into German.]
Bei sipgate haben wir supergute Erfahrungen mit regelmäßigen (alle 2 Wochen) Open Spaces gemacht. Auf Englisch habe ich dazu schon mehrfach gesprochen und geschrieben. Inzwischen gibt es den kompletten Erfahrungsbericht auch auf Deutsch, bei der Informaktik Akuell. Wenn Dich nur das Ergebnis und weniger der Weg dahin interessiert, findest Du im sipgate-Blog eine kürzere Variante.
If you’re even remotely interested in Coaching, I highly recommend “The Coach’s Casebook” by Geoff Watts and Kim Morgan. I’ve just finished it and it absolutely lived up to the raving reviews I read on Twitter! For the record, I’m a coaching newbie. I’d figure that newbies and intermediates will gain the most.
The book looks at 12 specific human traits ranging from Perfectionism to Fierce Independence to Procrastination. For each trait they look at a fictious yet very concrete case that’s based on reality. It’s a first person narration from the perspective of the coach and very relatable. The coach’s supervision with their own coach is part of this and really underlines the importance of supervision. Then come 3 methods that one could use to support someone with the respective challenge. At the end of each chapter is an interview with a successful person that overcame the trait.
Of all of these, I could have done without the interviews. They didn’t always seem relevant to me. I love the case studies and the methods. You get to see a wide range of approaches and the inner workings of the coach on top. I’ve learned tons and highly recommend it!
Have you seen this cartoon lately? With the caption “How it feels to watch a user test your product for the first time”
I laughed when I first saw it. I’m pretty sure I’ve retweetet it from this guy (his source (their source)). Ever since, I can’t shake the feeling that I betrayed my User Experience education. Yes, that cartoon captures what it feels like to watch users try to use something you created. You think you made it obvious, when you didn’t.
But I’d bet that for most people who retweeted the cartoon it seemed to capture what users behave like, thus continuing the “users are stupid” narrative. That’s why I made this:
There, I fixed it. Sorry for the crude drawing. I hope my UX honor is restored.
PS: From the conversations on Twitter it’s perfectly clear that the guy who tweeted it is aware that the designer is to blame. It’s less obvious to people without an UX background.
What a blast! We (sipgate) just hosted Richard Sheridan, CEO of Menlo Innovations and author of “Joy, Inc.”. Both, the real life Rich and his book are very entertaining and inspiring. So much so, that I’ll write a small series. I want to help spread the word about:
For starters, here are my favorite quotes (okay, passages) from the book:
“You can’t invite users into your office and ask them what they want, because they don’t actually know what they want. It’s not because they are stupid; it’s quite the opposite. They are unconsciously competent at what they do all day, so they can no longer deliver the most important minute details simply because they are unaware of them. The only way to get around this limitation is through keen and patient observation.” – Page 111
That’s where High Tech Anthropologists come in handy.
“To truly run an experiment, you need to try something out more than once, because at first – no matter what you try – it will probably be bumpy.” – Page 132
“[A]n aspect of scaling that no one ever considers: scaling down.” – Page 195
Indeed, when do we ever consider scaling down? “Scaling” in everyday tech use only knows one direction.
“We have always felt that our contracts […] should be ones we’d be comfortable signing no matter what side of the table we were sitting on. When we receive contractual terms from our clients, many of them are completely one sided; it is left as a difficult exercise for us to add in terms that protect our interests. We see this as incredibly wasteful and a terrible way to begin a relationship between two companies.” – Page 224
In other words, ye olde “Do unto others as you would have others do unto you” is universal, even and especially for contracts 🙂
Have you read the book? What’s your take on it?
Last week I spoke at the International PHP Conference aka Webtech Conf 2015 in Munich.
My talk “The Long Way to Lean” was the story of sipgate’s ongoing journey from traditional silo-ed company to agile and lean via Scrum. Find the slides & speaker notes here. There was a camera, so I hope I can eventually add a link to the video *fingersCrossed* Stay tuned 🙂
For a long time I’ve wanted to group the helpful 1-pagers on Wall-Skills.com into books (well, PDFs), so that it’s easy to study or display all those for a certain topic.
The topic currently dearest to my heart is a collection for Product Owners that are just starting out. That one’s still in the making but 2 sub-collections (they are gonna be chapters in the big one for Product Owners) are done and live on LeanPub: Facilitation (free!) and Agile & Scrum. Let me know what you think!
Update January 24th, 2016: “Skills for Successful Product Owners” is available 🙂