Chief Process and Innovation Officer (CPIO) or sometimes just Chief Process Officer (CPO) is a corporate C-level position that calls for a leader who is able to identify which parts of a company's business processes could be improved and identify specific ways to make them work better. Industry watchers like author Peter Hinssen and Michael Hammer propose that as IT moves towards a more service-oriented architecture and cloud computing, the traditional role of CIO as technology expert will evolve into that of a more process-oriented business supervisory role and the CIO will become the CPIO. Industry watchers like author Peter Hinssen and Michael Hammer propose that as IT moves towards a more service-oriented architecture and the cloud, the traditional role of CIO as technology expert will evolve into that of a more process-oriented business supervisory role, the CPIO.
Core competencies for a CPIO include:
Professional - The CPIO knows how his business works, is aware of innovations in Information Technology and is familiar with relevant IT service providers and vendors.
Social - The CPIO demonstrates leadership skills, including the ability to listen to employees, collaborate and network with other C-level managers and negotiate with vendors.
Managerial - The CPIO is able to run a department, oversee staff development, balance a budget and manage IT as part of a business function.
Transformational - The CPIO is comfortable with managing change -- both low-tech and high-tech change and changes in business goals.
Business - The CPIO is familiar with his market and actively monitors the competition.
Innovation - The CPIO is able to demonstrate which innovations will be worthwhile, determine how technology can further improve the business process and successfully market his ideas for change.
Click here for source article.
Thursday, February 12, 2009
Love this title - "Chief Process and Innovation Officer (CPIO)"
I got an email recently that had this description - I think this is my new dream job - having the authority to actually improve processes BEFORE implementing systems.
Subscribe to:
Posts (Atom)