Productivity @ Work
Singapore's productivity is lacking and according to sources cited in the link actual shrank in 2009 by 14.2 percent. Throwing in more hours (while being at the top of the world already) won't fix it, since productivity is (also) measured by "output per hour" and an increased output due to more hours worked won't change that. Our prime minister thinks that Singapore's productivity level is only 60%-70% of its potential. So in the typical hands-on-the-government-will-do Singaporean way a Productivity Portal has been created by the Singapore Government.
The site start with the introduction What is productivity: " Technically, productivity is the ratio of output to input. It is a measure of how efficiently and effectively a business or an economy uses inputs such as labour and capital to produce outputs such as goods and services" (emphasis from original source). Looking at the definition of productivity we meet two familiar terms: efficiency and effectiveness. Remember ISO 9241-11: " extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use." (emphasis mine).
So productivity and usability share their core properties. Making applications work well thus is not just a "nice-to-have" but an essential component of productivity improvements to accelerate value creation. Interestingly when calculating "value created" labour cost don't reduce the value, but are part of it, a refreshing departure from seeing workers as cost factors only. The website puts " Value Added = Sales of Output ($) - Total Cost ($) of Purchased Material and Services" (so your subcontractor _is_ a cost only). My friend Eric Mack states:
" Value created = Knowledge _ Methodology _ Tools". In IT we tend to focus on the tools, think to have some good grasp of knowledge but we are lacking in methodology. Sometime I wonder if we are caught in the The Knowing-Doing Gap . GTD is one method and there is no such thing as "no methodology" (at least if you count "I ignore tasks until someone screams" as methodology). Later this year there will be a conference focusing on productivity in Singapore.
The site start with the introduction What is productivity: " Technically, productivity is the ratio of output to input. It is a measure of how efficiently and effectively a business or an economy uses inputs such as labour and capital to produce outputs such as goods and services" (emphasis from original source). Looking at the definition of productivity we meet two familiar terms: efficiency and effectiveness. Remember ISO 9241-11: " extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use." (emphasis mine).
So productivity and usability share their core properties. Making applications work well thus is not just a "nice-to-have" but an essential component of productivity improvements to accelerate value creation. Interestingly when calculating "value created" labour cost don't reduce the value, but are part of it, a refreshing departure from seeing workers as cost factors only. The website puts " Value Added = Sales of Output ($) - Total Cost ($) of Purchased Material and Services" (so your subcontractor _is_ a cost only). My friend Eric Mack states:
" Value created = Knowledge _ Methodology _ Tools". In IT we tend to focus on the tools, think to have some good grasp of knowledge but we are lacking in methodology. Sometime I wonder if we are caught in the The Knowing-Doing Gap . GTD is one method and there is no such thing as "no methodology" (at least if you count "I ignore tasks until someone screams" as methodology). Later this year there will be a conference focusing on productivity in Singapore.
Posted by Stephan H Wissel on 14 February 2011 | Comments (5) | categories: Business