{"id":1711,"date":"2013-11-06T00:00:00","date_gmt":"2013-11-05T23:00:00","guid":{"rendered":"https:\/\/wwwneu.strehle.de\/tim\/weblog\/archives\/2013\/11\/06\/1665\/"},"modified":"2013-11-06T00:00:00","modified_gmt":"2013-11-05T23:00:00","slug":"1665","status":"publish","type":"post","link":"https:\/\/www.strehle.de\/tim\/weblog\/archives\/2013\/11\/06\/1665\/","title":{"rendered":"If I were a manager"},"content":{"rendered":"<p>I\u2019m an idealist who loves to daydream. For example \u2013 what would I do if I were a manager? I work as a \u201clead software architect\u201d, a fancy title that means I\u2019m still just a developer. (Which has its pros and cons.) Here\u2019s the entirely theoretical lessons I learned from watching others manage, and reading pieces on leadership on the Internet:<\/p>\n<p>First I\u2019d assume that our team is a group of hard-working, intelligent, rational, professional, <strong>self-managing grown-ups<\/strong> who do their own independent thinking and are happy to take responsibility. We all want to do a great job and want the company and our colleagues to be great, too. Each of us has unique strengths, sees things that others overlook, and has an opinion that matters as much as everyone else\u2019s. The team organizes itself, everyone takes on the next thing that\u2019s important to work on.<\/p>\n<p>In this environment, management mostly means <strong>helping to remove impediments<\/strong> which the team finds keep them from being productive. Interactions with other parties (other departments, customers) need to be scheduled and organized. Information must flow freely and tools work smoothly. The team needs help setting up spaces to review, reflect, encourage and criticize each other\u2019s work. An occasional conflict needs mediation. Decisions have to be made in time (often by the team, but someone\u2019s got to drive the decision making process).<\/p>\n<p>I\u2019d make <strong>almost all company information transparent<\/strong>, make sure that everyone has an up-to-date overview of the company financials and the work everyone\u2019s currently doing. And of the work that lies ahead: all the features and deadlines we promised to our customers and partners. Sales people would be asked to bring photos and reports from their visits to potential clients. Developers would, where possible, publish screencasts of their work. We\u2019d tell each other more stories of our day-to-day work, and help everyone see the big picture. This, I\u2019m convinced, would make us grow together, increase motivation, uncover hidden problems and improve our decision making.<\/p>\n<p>And we\u2019d obsess over what is delivered, not over processes and rules. I\u2019d try to spark a passion for the customer, to get everyone <strong>closer to the customer<\/strong>, closer to the problem. Make it our own problem, either because we\u2019re using the thing ourselves or because we\u2019re personally being held responsible by a customer. Ain\u2019t it funny how priorities change when a developer visits a customer and brings back a list of things to do, knowing he\u2019ll have to return in two weeks and report on the progress?<\/p>\n<p>Other essentials: Be honest, admit your own faults freely but don\u2019t point others\u2019 out. Be understanding and forgiving and kind. Help others to focus and learn and grow. Find the right combination of pragmatic, elegant simplicity and quality\/excellence \u2013 we\u2019ll need both for our products to survive.<\/p>\n<p>Let\u2019s hope that I\u2019ll never become a manager\u2026 I sure wouldn\u2019t be able to live up to these ideals! (Hey, maybe the leader position can rotate between team members?)<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I\u2019m an idealist who loves to daydream. For example \u2013 what would I do if I were a manager? I work as a \u201clead software architect\u201d, a fancy title that means I\u2019m still just a developer. (Which has its pros and cons.) Here\u2019s the entirely theoretical lessons I learned from watching others manage, and reading [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","_share_on_mastodon":"0"},"categories":[1],"tags":[],"class_list":["post-1711","post","type-post","status-publish","format-standard","hentry","category-weblog"],"share_on_mastodon":{"url":"","error":""},"_links":{"self":[{"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/posts\/1711","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/comments?post=1711"}],"version-history":[{"count":0,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/posts\/1711\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/media?parent=1711"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/categories?post=1711"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/tags?post=1711"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}