Skip to main content

Breaking Hierarchies, and the birth of a Network Organisation at a Pure Project Based Company

It is an exciting and tiring time at Actum.  We are growing and changing at rapid pace, such a growth brings on new challenges and experiences that none of us, including founders had before. Most of the experiences are new to us all. None of us experience 300% or more growth in couple of months, and this is what is happening to several teams and departments currently. Right people and right attitudes are key factors in our growth and success so far. 

In any traditional organisation, growth brings on new hierarchy - more Directors, Team Leads, VPs and etc. However, we decided to go the opposite and reduce hierarchies as we grow. One of the Founders is leading such change initiative. He is brave enough to experiment it and allows the rest of the organisation to shape the idea into a more practical one. 

Actum is a project based company, we develop software, consult on digital strategy and customer experience, and we also help clients with processes (Lean, Agile, Design Thinking, Kanban, …). The organisational change we are going through now was never done in a project based company, or at least we do not know about any other example, so please share with us if you know a pure project based company (Digital Agency or Software Company) doing what I am going to describe below. We love to learn from others successes and failures 😉

What started to happen and will continue:

- We will not build teams for projects any more, but we create cross functional (generalised specialist) teams that move from one project to another. This allows stability within teams. 

- So, we will not allocate resrouces to projects any more, but we will allocate projects to teams. And eventually (in the next steps of evolution) teams will pull new projects as they are available, instead of somebody assigning them a project. 

- Whoever wants to change the team, should agree with his current and target team members. 

- A pool of projects will allow us to manage portfolio of Clients and Projects based on capability and fitness criteria (KPIs) that have meaning to clients. 

- Supportive and Domain Expert teams will provide service to each project team just-in-time. 

- We will build Innovation Team, Software Archite Team and other supportive groups such as HR, IT and Finance. 

- A network of Kanban will allow different teams to provide services to each other, and continues improvement metrics and change management nature of kanban makes sure that we improve forever. 

- We allow crews to shape on demand to handle certain situations or a short term task that requires expertise from different groups and teams. 

The bottom line is that, we will have stable and autonomous teams working with other supportive teams and experts to deliver solutions and continuously improve the way they work within a network organisation. We expect each team to improve differently and only influence each other. 

There are a lot more details to this change, But that is enough writing for now ;)  We will see the manifestation of the above initiatives in the next months, and I will share them as they happen.


Comments

Popular posts from this blog

Business & Economy - Wall Street Crash & U.S. sub-prime market (Part 1)

History of economy would suggest that once every couple of generations there is a complete prosperity-depression cycle that occurs within the financial market, and economy as a whole. The last time this happened was in the 1920’s, and 30’s. It started with the Wall Street Crash of 1929, and then it moved through to the Great Depression and ended beyond World War II. The current global financial and economic situation resulting from crisis caused by the U.S. sub-prime market appears to be the start of one of these historic cycles at this point in the maturation of the human race. Despite the fact that U.S. economy is in recession, there are many contradictory opinions about another financial and economical crisis. The purpose of this blog is to clarify similarities and differences between the economical events in 1920's, and 30's with current global financial and economic situation. The twenties in America were a very good time. Production and employment were high and rising....

Business & Economy-Confused Branding Part 1

I came back to Tehran to live for some months after 4 years. It seems that we had a boosting advertising market, people started to talk about Marketing Strategy, Marketing Research, Companies started to open positions in Marketing Management, Advertising Management fields. Yes, I know it is little bit funny and too much sad, Since all other countries started to think about this science more than 50 years ago!! But I would be proud of all these Iranian companies, who started to Re-Think Marketing, if they walk what they talk! I do not know how many billboards have been installed in highways since 4 years ago, I just can say too much.This is good, because it represents a progress in Marketing culture, but you can see unknowledgeable Marketers and greedy advertisers in confused companies with uncertain management strategy in all those advertising. One of these companies called "TAK MAKARON". They are the biggest pasta producer in Iran. TAK MAKARON has started when there ...

Moving from Basic DAD Scrum Based LifeCycle to Continues Delivery (Kanban Based) Lifecycle

I was thinking what the title of this blog post could be, I had couple of options to select from and decided to use a title that uses Disciplined Agile (DA 2.0) Lifecycle. Other options for titles were: Moving From Scrum to Kanban From High Performing Scrum Teams to Hyper Performing Kanban  The bottom line is that at some point you may want to move away from Time boxes to a flow of work and service oriented teams and improve performance and throughput without massive and sudden organisational change.  As always, I only share my experience and this may not apply to all situations, context is important.  Another reason that I selected “Moving from Basic DAD Scrum Based LifeCycle to Continues Delivery (Kanban Based) Lifecycle” as the title, was that for many it is a question mark how to navigate through DAD life cycles. and I think this blog post could be one of the ways to navigate.  Context: A Delivery Team started with Type A Scrum with 2 weeks Sprin...