{"id":1708,"date":"2011-01-26T17:24:10","date_gmt":"2011-01-26T19:24:10","guid":{"rendered":"http:\/\/blog.plataformatec.com.br\/?p=1708"},"modified":"2011-01-28T14:48:52","modified_gmt":"2011-01-28T16:48:52","slug":"six-good-practices-that-have-improved-our-team-productivity-plataforma-tec-full-version","status":"publish","type":"post","link":"https:\/\/blog.plataformatec.com.br\/2011\/01\/six-good-practices-that-have-improved-our-team-productivity-plataforma-tec-full-version\/","title":{"rendered":"[full-version] Six good practices that have improved our team productivity \u2013 The Plataforma Tec Way"},"content":{"rendered":"
[as some of you might have noticed, I\u00a0accidentally clicked on “Publish” on my draft version, here is the full version\u00a0of the post. Sorry about that]<\/p>\n
*Though this blog post was written for any audience, there is a chance that you’ll be more interested if\u00a0\u00a0you are a\u00a0startuper<\/a> or running a\u00a0knowledge workers<\/a> based company.<\/em><\/p>\n A year ago I was writing about a few\u00a0uncertainties\u00a0that we faced while starting up Plataforma Tec<\/a> and how we dealt with them. We know that we still have a lot to learn,\u00a0but now that another 12 months have passed by we are feeling much more solid and confident about what we’re building.<\/p>\n As last year’s post, this will also be about sharing our thoughts and\u00a0a few practices that have been helping us a lot in creating a\u00a0company culture\u00a0and\u00a0leveraging\u00a0our team into its best.\u00a0I hope you enjoy and find them useful!<\/p>\n what a team! =D<\/p><\/div>\n We believe that (…)<\/strong><\/p>\n 1)… mastering our work IS our work<\/strong><\/p>\n <\/strong><\/p>\n "better and better and better"<\/p><\/div>\n We constantly tell people and customers “hire us only if you need a well developed application” (for example: a web application that will provide a revenue stream or will constantly have new features). This is one of our main assets and our main\u00a0differentiation\u00a0in this price competitive industry. Frankly, this strategy has been working fine for us but in order to keep it running this way, we are\u00a0constantly looking for\u00a0mastering our work all the time. Otherwise, if we don’t, there will be a great chance of losing our competitive\u00a0edge.<\/p>\n 2)… responsibility comes along with autonomy<\/strong><\/p>\n "with great power, comes great responsibility"<\/p><\/div>\n<\/dt>\n<\/dl>\n<\/div>\n In last year’s post we mentioned that we only hire professionals that we feel\u00a0comfortable\u00a0giving autonomy, but it’s important to remember that it must be used very carefully. So,\u00a0although autonomy makes a great pair with the constant search for mastery, don’t forget to be very cautious when dealing with\u00a0decisions\u00a0that might have a great impact in your company. We usually handle this kind of situation with two simple practices:<\/p>\n 3)… gathering \u00a0the team to discuss problems is a great way to find solutions<\/strong><\/p>\n gather your team and discuss problems and solutions<\/p><\/div>\n Once in a while we face\u00a0situations\u00a0that are a bit more risky or complicated to be solved by our selves alone. They can be technical or design problems, a project\u00a0management\u00a0issue or even a simple warm-up for a business meeting. For all this we usually gather two or three team mates to ask for their opinion and discuss about the options that we might have.<\/p>\n 4)… projects managers shouldn’t delegate work or\u00a0establish\u00a0random deadlines. They should serve and protect the team from undesired noise.<\/strong><\/p>\n "to protect and serve"<\/p><\/div>\n<\/dt>\n<\/dl>\n<\/div>\n In our company, projects managers, salesmen and organization leaders work together with developers and designers. We see it as a system that must work synchronized. Also, the actions of\u00a0planning,\u00a0estimating\u00a0and taking\u00a0decisions in a project\u00a0\u00a0should be made by the whole team (and not only by the manager). We found out that serious problems might arise when this system is desynchronized or made only by one person.<\/p>\n In our opinion, the manager role is to assure that developers and designers have the proper atmosphere to do their best. And by ‘proper atmosphere’ we mean that they have to provide the right tools (hw and sw), proper workplace, avoid useless\u00a0interruptions\u00a0and support the team when they get stuck with something.<\/p>\n 5)… establishing roles is good and we avoid hierarchy levels<\/strong><\/p>\n do not create communications layers between team and managers and leaders<\/p><\/div>\n Some managers try to list and predict 100% of the problems that might happen in a project. Here at Plataforma Tec, we assume that it’s impossible to do so. Therefore the big deal is NOT about trying to predict and avoid 100% of the problems. The deal is to BE PREPARED TO REACT when a problem happens and trying to avoid the most obvious problems that could happen.<\/p>\n Ok, but what does it all have to do with\u00a0Roles vs. Hierarchy<\/strong>? So,\u00a0that’s where\u00a0hierarchy\u00a0kicks in… there is a great chance that creating\u00a0hierarchy levels will degrade the communication quality<\/a> in you company. This is one of the reasons we avoid creating different levels here at Plataforma Tec. Instead, we prefer defining roles. Developers should develop, Managers should support, Salesmen should sell (but synced with the whole “system” mentioned in item “4”).<\/p>\n If you’re having trouble understanding the difference between Roles and\u00a0Hierarchy, take a look at Scrum’s roles (as an example of\u00a0definition\u00a0of roles).<\/p>\n 6)… business leaders must create the right policies to enable all the items above<\/strong><\/p>\n policies should be discussed, not imposed<\/p><\/div>\n<\/dt>\n<\/dl>\n<\/div>\n All these practices won’t be effective if the organizational leaders don’t believe and provide the right policies to really enable them. Important notice: be careful not to confuse policies from impositions.<\/p>\n Well, this is a list of a few things that we’ve been doing and they have worked fine for us. Also,\u00a0these six practices will work a lot better if implemented together, since they leverage each other.<\/p>\n I guess that’s it and I hope they’ll be useful or inspiring to others. Also, don’t forget to comment what you think about this small list of practices… Do you think they’ll work in your company?<\/p>\n","protected":false},"excerpt":{"rendered":" [as some of you might have noticed, I\u00a0accidentally clicked on “Publish” on my draft version, here is the full version\u00a0of the post. Sorry about that] *Though this blog post was written for any audience, there is a chance that you’ll be more interested if\u00a0\u00a0you are a\u00a0startuper or running a\u00a0knowledge workers based company. A year ago … \u00bb<\/a><\/p>\n","protected":false},"author":6,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"ngg_post_thumbnail":0,"footnotes":""},"categories":[1],"tags":[135,136,134,52],"aioseo_notices":[],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/blog.plataformatec.com.br\/wp-json\/wp\/v2\/posts\/1708"}],"collection":[{"href":"https:\/\/blog.plataformatec.com.br\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.plataformatec.com.br\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.plataformatec.com.br\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.plataformatec.com.br\/wp-json\/wp\/v2\/comments?post=1708"}],"version-history":[{"count":20,"href":"https:\/\/blog.plataformatec.com.br\/wp-json\/wp\/v2\/posts\/1708\/revisions"}],"predecessor-version":[{"id":1717,"href":"https:\/\/blog.plataformatec.com.br\/wp-json\/wp\/v2\/posts\/1708\/revisions\/1717"}],"wp:attachment":[{"href":"https:\/\/blog.plataformatec.com.br\/wp-json\/wp\/v2\/media?parent=1708"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.plataformatec.com.br\/wp-json\/wp\/v2\/categories?post=1708"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.plataformatec.com.br\/wp-json\/wp\/v2\/tags?post=1708"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}<\/a>
<\/a><\/strong>
\n
\n
\n
<\/a>
\n
<\/a>
\nCheck this: if we are prepared to react to a problem, first we must DETECT the problem. Right?<\/p>\n\n