<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Mikko Henrik Pitkänen on Medium]]></title>
        <description><![CDATA[Stories by Mikko Henrik Pitkänen on Medium]]></description>
        <link>https://medium.com/@mikkohenrik?source=rss-b4622524933a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*R8_kXYwHhCnEhMG8EMlDiQ@2x.jpeg</url>
            <title>Stories by Mikko Henrik Pitkänen on Medium</title>
            <link>https://medium.com/@mikkohenrik?source=rss-b4622524933a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 08:11:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mikkohenrik/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Bid Manager vs. Project Manager]]></title>
            <link>https://medium.com/@mikkohenrik/bid-manager-vs-project-manager-fa5b6b1366d7?source=rss-b4622524933a------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa5b6b1366d7</guid>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Mikko Henrik Pitkänen]]></dc:creator>
            <pubDate>Sat, 18 Feb 2017 11:02:59 GMT</pubDate>
            <atom:updated>2017-02-18T11:02:59.750Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Bid Manager vs. Project Manager</strong></p><p><em>Having a background in project management is great when you are faced with the task of planning a new project. However managing a bid or writing a proposal is fundamentally different from managing a project.</em></p><p>There are two main differences between bid management and project management.</p><p><strong>Following the facts</strong></p><p>When doing a project you already know what you have to do, by when and how much can it cost. That is called the iron triangle of project management: quality, time and cost. Those are contractual facts. Your goal is to stay in scope, spend available resources and make it in the timeline that is written down in the plan. You can sometimes make exchanges between shorter timeline for more resources, smaller scope for less money to spare, but sometimes not even that because of dependencies to partners or other projects. And if your scope creeps or explodes you will have to look for more money and resources to finalize.</p><p><strong>Co-creating the plan</strong></p><p>When writing a bid or a project plan you basically have no time, no money and no resources – and you have to invent how you would spend it if you had it. The work that results from these constraints is at best fast, lean and collaborative. – at worst it is slow, complex and you are all alone. To get it right you have to get attention from technical, sales, legal and business experts as well as other managers and senior level sponsors to get comments or approval. And none of them has any intention of doing your job for you. They are always busy but you have to get their attention in order to succeed. But if you fail, it’s not their fault. Typically the expertise is scattered around the organization and in networked project consortia between organizations and in different countries. When you have these domain experts collaborating it is great, but they are sometimes also negotiating against each other and competing with partner companies. And your job in planning the project is to pull this all together in a very short deadline. And if you make it, the bid will end up being a contract that your project managers have to deliver. I hope it was not messy all the way till the end, right?</p><p>There is a fundamental difference in managing a bid and managing a project. In bid writing you have to invent the project that is feasible, winning and profitable. When managing a bid that has been won the project manager has to deliver the plan and manage the risk from day one to keep it going also in real life. Sometimes project plans propose theoretical alternative truths but when the reality hits the fan and it is the project managers job to clean it up. The luxury is that a project manager already has a project plan, funding and timelines to follow – you know what needs to get done at least with the available resources to make dreams come true.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa5b6b1366d7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Professional identities vs. building cross-disciplinary skills]]></title>
            <link>https://medium.com/@mikkohenrik/professional-identities-vs-building-cross-disciplinary-skills-3634e00cba9b?source=rss-b4622524933a------2</link>
            <guid isPermaLink="false">https://medium.com/p/3634e00cba9b</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[design-thinking]]></category>
            <dc:creator><![CDATA[Mikko Henrik Pitkänen]]></dc:creator>
            <pubDate>Wed, 07 Dec 2016 14:51:44 GMT</pubDate>
            <atom:updated>2016-12-07T14:51:44.103Z</atom:updated>
            <content:encoded><![CDATA[<p>In R&amp;D teams building cross-disciplinary skills is the key to success. The best new things are invented in-between domains, by lending, re-using, mixing and matching validated operating models and ideas from another discipline. But what skills should you have in person and on what task should you collaborate with cross-disciplinary expertise?</p><p>At the team level the professional expert has two ways to learn more: deepen the domain specific skills or diverge to learn new skills. In R&amp;D teams the best composition is a small team made by matching experts from various disciplines e.g. from technology (T), design (D), and business (B). To give an example we could consider that tech design and business are expertise of persons A, B and C. The combinations could be AT, BD, CB.</p><p>Here we have Andy who knows tech (AT). Andy has Claire working with business case (CB) and Bob who is a designer by virtue (BD). They all know their stuff and work efficiently on solo. They are also collaborative and nice people in person. There comes the 3 month project and they plan, execute and deliver like professionals do. But in their real life they like to learn new things too. If Andy would like to learn business he would need to listen carefully what Claire is saying and doing. But in a team composition, Andy is the tech-guy and would not be the best fit for an AB role. So what should Andy do in terms of professional development and to maximise the learning value in a project? On short term he should dig deeper into tech and stay in the specialist role that he has crafted for himself. He is prepared for the interdisciplinary team work, trusting that relationships are more meaningful and bring more results than personal multi-capabilities. He doesn’t believe in superheroes either. In the next project Andy is even sharper and more productive and he gets a career flow from project to project as the AT guy to have take care of your tech stuff in the trickiest problems.</p><p>From a managerial point of view it may be smart to have Andy, Bob and Claire work together for several projects. If they learn to work together and deliver great value, they will also make a nice profit for the company. But for R&amp;D and innovation, where you need to keep making things differently, they will need to keep moving both intellectually and collaboratively. Each team will eventually form a pattern and get stuck in their way of working. This is why many of us like working in projects: to learn more and do new things (or the same things) with new people.</p><p>In the interdisciplinary team working mode the project manager should coach Andy, Claire and Bob ( …we almost forgot about Bob! And he is not even in the picture because he just made the design and thinks it’s cool not to show off.) They should be supported in developing their specific professional skills and have them hand picking to join new teams and extend their professional networks. This way they are able to generate different outcomes from similar project assignments. In the long run also Andy will learn a lot about design and business, but it takes a long time to be self-sufficient in a new skill. I suggest that professional identities should be deepened at the short term and extended in the long term when working in cross-disciplinary R&amp;D projects.</p><p><em>This post was originally published in Propellerhat Management blog </em><a href="http://propellerhat.co/"><em>propellerhat.co</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/856/1*Qt9l_ZL0DZjkmtpo1q-62A.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3634e00cba9b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Intellectual Capital]]></title>
            <link>https://medium.com/@mikkohenrik/introducing-intellectual-capital-1d8ff5addf3d?source=rss-b4622524933a------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d8ff5addf3d</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[venture-capital]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Mikko Henrik Pitkänen]]></dc:creator>
            <pubDate>Mon, 05 Dec 2016 08:52:06 GMT</pubDate>
            <atom:updated>2016-12-05T08:52:06.130Z</atom:updated>
            <content:encoded><![CDATA[<p>What is Intellectual Capital? Intellectual capital was first published by John Kenneth Galbraith in 1969. His belief was that intellectual capital meant more than just “intellect as pure intellect” but more like an “intellectual action”. In a sense intellectual capital is not a static asset or object of value but an ideological process — a means to an end.</p><p>Who owns intellectual capital? Ownership of intellectual capital is a controversial issue. Firstly, intellectual capital it is immaterial, not visible like machines, facilities and financial capital. Secondly, defining a specific intangible resource is difficult and depends on the person or institution defining it. Thirdly, it is not totally owned by the company, if you take as an example the employees capabilities and competences. This also makes buying intangible resources, like company culture, impossible (the usual exceptions are patents and copyrights) while physical resources can easily be purchased and sold.</p><p>Who is an intellectual capitalist? Intellectual capitalist is a manager who gets things done and promotes intellectual activity in the organisation or the team. This is done to support human centred development, organisational ways of working and relationships with customers. The human, structural and customer centric focus is a winning formula in any company that values its success in terms of intellectual capital. Therefore we can call a manager who owns and invests his or her intellectual capital an intellectual capitalist.</p><p>How to make more intellectual capital?</p><p>Intellectual capital is really like virtual money. You can make more of it by learning, interacting, contracting with partners who create value — and you can spend it to invest in your company or project.</p><p>In fact by spending this kind of a resource on a good cause and results you actually gain more and do not loose your own baseline assets in the bargain. Basically you shape the “diamonds” of intellectual capital by accomplishing tasks that generate desired value. It is a win win for all contributors. You can also loose intellectual capital by making poor choices, bad products and destroying good relationships.</p><p>Intellectual capital is a brand value that is fragile and hard to grasp — both as a concept and as a resource to be quantified. But when you have adopted a way of nailing it down and measuring it’s growth you can use that to leverage and grow your company. Then we can say that — congratulations, you are on your way of becoming a top intellectual capitalist.</p><p><em>This post was originally published in Propellerhat Management blog </em><a href="http://propellerhat.co/"><em>propellerhat.co</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/856/1*Qt9l_ZL0DZjkmtpo1q-62A.png" /><figcaption>© Propellerhat Management Oy 2016</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d8ff5addf3d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>