Category: Team Insights
-
Most people who work in product development agree that it is essential to understand key problems in order to build good solutions. This often involves understanding the customer or finding new products. It has also become common for engineers, who are responsible for building the product, to be involved from the start. This is explained…
-
In my last blog post, “The Framework Trap,” I talked about all the problems we ran into when engineers, designers, and product team members were working together. I’ve come to see that Scrum, with its strong emphasis on the right processes, has actually been more of a hindrance than a help to our team. While…
-
When we started working on our products, especially our software, we had a pretty inexperienced team. Some of us had already worked on software projects at other companies or participated in research projects at universities or research institutions. The team’s most experienced member, in terms of years of professional experience, was a software engineer with…
-
Over the past 12-18 months, we have established the initial structures for a middle management level within our company. The reason for this was that the number of employees had increased significantly from just under 10 to over 30, which would have resulted in a management depth of around 15 people with only two founders.…
-
When newcomers join the team, there are often significant differences in how quickly and how well they perform their assigned tasks. Basically, I have identified the following types, which I would like to link to learning curves: In the following, I would like to outline the possible reasons for the increasing returns pattern and what…
-
Young start-ups often have a large number of tasks and at the same time very few hands and minds to handle them. For example, smaller startups with fewer than 15 employees often have no dedicated support functions such as back office staff to take care of office organization, bookings, invoices, etc. This is often the…