<?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 Bosa Igbinoba on Medium]]></title>
        <description><![CDATA[Stories by Bosa Igbinoba on Medium]]></description>
        <link>https://medium.com/@bosaigbinoba?source=rss-905e40c4bee9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*0wNrFKxWfBlNi__3olid5w.jpeg</url>
            <title>Stories by Bosa Igbinoba on Medium</title>
            <link>https://medium.com/@bosaigbinoba?source=rss-905e40c4bee9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 13:43:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bosaigbinoba/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[The Importance of Business Analysis in 2024]]></title>
            <link>https://medium.com/agileinsider/the-importance-of-business-analysis-in-2024-4e9e8f721ee?source=rss-905e40c4bee9------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e9e8f721ee</guid>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Bosa Igbinoba]]></dc:creator>
            <pubDate>Mon, 08 Jul 2024 17:31:35 GMT</pubDate>
            <atom:updated>2024-07-08T17:31:35.283Z</atom:updated>
            <content:encoded><![CDATA[<h4>Business Analysis is more important than it’s ever been!</h4><p>Business Analysts (BAs) aren’t as “trendy” or as “glamorised” as Product Managers, but there are significant skill overlaps. BAs tend to get their hands dirty, keep things moving and ensure there’s a cohesive bridge between business and tech.</p><p>If you’re a business owner, decision maker, run a department or have some influence over who is hired then this piece is for you. Any tech upgrade, product build or project work requires consistency and cohesion between business and technology.</p><p>If developers can be assimilated into the business, then great. However, this isn’t always the case. In fact, developers can often feel marginalized due to a disjointed approach, cultural differences, or lack of clarity; this is where a good business analyst comes in, a pro who ensures that the critical bond between business and tech remains in tact. <a href="https://www.quora.com/Why-does-it-seem-that-so-many-companies-treat-programmers-so-poorly">Check out this Quota post where some software developers lament how they are treated.</a></p><p>There’s one profession that is agnostic of industry, domain, and department and that is business analysis.</p><p>Whether you’re a small business owner looking to scale, or you’re a CEO of a large corporation, understanding business analysis as a profession could help your business substantially. Not necessarily to embark on a hiring spree but understanding the value business analysts can provide could help you make better decisions when delegating tasks, hiring correct personnel for project work, and producing a more streamlined, more effective project team. Without streamlined teams, business change is more difficult that it must be.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*vqyvIToTSI1Hkpps.jpeg" /></figure><h3>‍‍Background</h3><p>The fluidity, flexibility, and pragmatism of the workplace in 2024 means more and more people benefit from having transferrable skills, adopting a flexible approach in the workplace and employment transparency between employer and employee is more important than ever; things like being clear on career goals, hobbies, aspirations and so on are increasing in importance.</p><p>Whilst job titles will always have a place in the labor market, skills, experience, and adaptability is becoming more important than ever.</p><p>In the advent of hybrid working, the fusion of home working with semi-regular office trips symbolizes the revolution that has taken the world by storm since 2020. Moreover, employers now know to keep hold of talent and to ensure they remain competitive in terms of attracting talent they must be flexible.</p><p>The same goes with employees.</p><p>Whilst being a jack of all trades, master of none is not advisable, there are some professions that lend itself to this new employment wave and one of these professions is business analysis.</p><p>In short, a business analyst is a conduit that usually sits between business and technology. A business has a problem they seek to solve with technology, so to remain cohesive, a business analyst creates a bridge between the disparate teams to ensure transparency, productivity, and organization.</p><h3>Product Enhancements and Project Work</h3><p>As we all know, we all rely on technology for so much today and that reliance means products must be maintained and enhanced consistently to provide customers with continued value and to increase revenue for the service provider.</p><p>This means that all businesses must ensure they have an in depth understanding on the software development lifecycle, the product lifecycle and what it means to consistently maintain and improve software solutions.</p><p>In the recent past, a product solution might start off small during the MVP phase, where the main business and technology people ratify, analyze, and conduct most of the work themselves; this was quite normal. This kind of work however is not sustainable if a business wishes to scale.</p><p>A specialist whose entire profession is focused on gathering, analysing, documenting, and presenting information will eventually be required; this will make your internal processes more efficient and focused, which should free up SME resource so they can focus on more refined, specialist tasks and not get bogged down with essential, but time-consuming project work.</p><p>Here are some common signs that your company may lack a specialist analyst:</p><p><em>- Many unknowns with regards to understanding the product, industry, project, or market</em></p><p><em>- Requirements missed, causing delays in solution development</em></p><p><em>- Project scope unclear, leading to confusion and inefficiency</em></p><p><em>- Scope creep, too many requirements and a general misunderstanding of what requirements</em></p><p><em>- Lack of project/product structure</em></p><p>There are more reasons, but the list above is a snapshot as these are the most common shortcomings in projects today.</p><p>Having business analysts’ part of any software endeavor tends to add value in the areas listed and having professional specialists, whose sole role is to ensure there is consistency between business and technology means SMEs can spend their time in their areas without having to compromise their time, effort, and energy.</p><p>Ask yourself, have you been part of a failed project that failed because of one of the reasons listed above?</p><p>The heavy dependence and reliance on technology means businesses cannot afford to allow the above list to strain their resources for too long; market share losses, lower workplace morale and a dip in performance could be the result if projects don’t succeed and this could be sustained if the correct personnel are part of the team.</p><p>Moreover, any senior decision maker would bode well by understanding the basics of business analysis so that if hiring becomes an option they know what to look for, how to assess candidate credibility and how best to deploy them in the team should they join.</p><h3>Industry Agnostic</h3><p>From marketing, to finance, from HR to sales, business analysis as a discipline permeates and penetrates many departments and industries.</p><p>All businesses have some form of finance, sales, marketing and HR functions, business analysis lends itself to almost all industries of all sizes due to the specifics a business analyst is expected to do.</p><p>Whilst domain knowledge is essential for any business analyst to be effective, the raw, fundamental skills remain the same regardless of industry.</p><p>For example, a business analyst who has worked on banking projects might not be able to transfer to an insurance project due to the specialization in one domain, the same is true of a person who has worked in FMCG and wishes to work in fashion for example.</p><p>Domain knowledge is essential. However, a professional with good domain knowledge in one area who is seeking a career change may consider a career as a business analyst due to the rewards and responsibility business analysts tend to get.</p><p>Certain tasks such as business process modelling will require a good understanding of the said domain, the nuanced aspects of that industry will provide the framework in which the analysis will be built upon.</p><p>So, the more you know about the domain you work in, the better the analysis and the richer the results provided by the business analyst.</p><p>So, whilst business analysis is an essential part of the modern workplace, without the business analyst possessing good domain knowledge their skills and analysis will be lacking.</p><h3>Salaries</h3><p>According to <a href="https://www.glassdoor.co.uk/Salaries/london-senior-business-analyst-salary-SRCH_IL.0,6_IM1035_KO7,30.htm?clickSource=searchBtn">Glassdoor the average UK salary is £63,746</a> with a “Very High” rating for job security. In the US, according to <a href="https://www.indeed.com/career/business-analyst/salaries">Indeed the average salary is $75,145.</a></p><p>Both figures suggest good salaries for modest levels of experience. Also, many business analysts have gone onto higher paying roles such as management consultancy due to the skills cultivated whilst they operated as a business analyst.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*b4JHVHyHztXChYf8.jpeg" /></figure><h3>Types of Business Analysts</h3><p>As a conduit resource positioned acutely between business and technology, the expectations and business needs will not only differ between organizations, industries and even departments, but the increased need for specialization ensures a more efficient way of utilizing business analysis resource.</p><p>This means that the roles listed below are all types of business analyst roles, but they are more focused on specific parts of the solution:</p><h3>Requirements Analyst</h3><p>If a role is explicitly asking for a Requirements Analyst, they usually want the business analyst to spend most of their time focused on the requirements.</p><p>Requirements Analysts would typically spend their time analyzing, documenting, and presenting requirements positioned between the business and development teams respectfully.</p><p>It’s likely to find requirements analysts usually in an “Agile” CI/CD environment where requirements are dynamic and there is a continual need to ratify, explain, improve upon, and define many requirements with considerable complexity attached.</p><p>The requirements analyst should know:</p><p><em>- Software development lifecycle (especially requirements gathering and testing)</em></p><p><em>- Technical writing for documentation</em></p><p><em>- Classification of requirements</em></p><p><em>- Presentation of requirements</em></p><p><em>- Requirements management</em></p><p>Furthermore, these tasks are part of the business analysis framework, but a requirements analyst tends to be more focused on requirements.</p><h3>Data Analyst</h3><p>We all know that data is gold dust today and our workplaces have more emphasis on analytics than ever before. In truth, a data analyst is also a bridge resource between business and development teams.</p><p>A good data analyst must be able to collect, store, structure and transform vast amounts of data. The presentation of this to stakeholders must then be understandable in a clear, well presented, and cohesive way.</p><p>Business analytics, business intelligence and a focus on data in general is the strategic focus from many companies and teams in today’s world. <a href="https://www.analystexchange.net/post/businessanalyticsandbusinessanalysis">You can read about the similarities and differences between business analysis and business analytics right here.</a></p><h3>Other Related Roles</h3><p>Business analysts may also have a particular preference, where they could be more business leaning or development leaning, either way, they join teams together. Other roles include:</p><p><em>- System Analysts</em></p><p><em>- Technical Business Analysts</em></p><p><em>- Configuration Analysts</em></p><p><em>- Business Enterprise Analysts</em></p><h3>Conclusion</h3><p>As a business owner, SME, department head and so on it certainly pays to understand the value business analysis can provide to you and your business.</p><p>Focused, specialized resource that allows SMEs to focus on their solution drives efficiency throughout the business and ensures your team can focus on what they are good at.</p><p>Business analysts add most value when they are understood and have clear mandates.</p><p>Whilst their role involves providing clarity to complexity, being able to paint the picture at interview stage will inspire confidence in the aspirant. Also, it always bodes well if you know what you want, so that time is not wasted.</p><p>Ensure you have a good grasp on what business analysis is, what value it can have and why you might benefit from incorporating these skills, personnel, and resource into your team.</p><p>‍</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e9e8f721ee" width="1" height="1" alt=""><hr><p><a href="https://medium.com/agileinsider/the-importance-of-business-analysis-in-2024-4e9e8f721ee">The Importance of Business Analysis in 2024</a> was originally published in <a href="https://medium.com/agileinsider">Agile Insider</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Cost of Project Failure — People, Processes and Technology]]></title>
            <link>https://medium.com/agileinsider/the-cost-of-project-failure-people-processes-and-technology-5acbd4806721?source=rss-905e40c4bee9------2</link>
            <guid isPermaLink="false">https://medium.com/p/5acbd4806721</guid>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Bosa Igbinoba]]></dc:creator>
            <pubDate>Sun, 03 Sep 2023 21:22:12 GMT</pubDate>
            <atom:updated>2023-09-03T21:22:12.152Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Cost of Project Failure — People, Processes and Technology</h3><p>Technology projects are industry agnostic, affect billions of people and are still rife with inefficiencies that lead to so many of them failing. Failure usually costs valuable time, money, effort, and other resources that are difficult or impossible to recoup.</p><p>Failed projects, ranging from <a href="https://www.thisismoney.co.uk/money/cars/article-8380881/New-images-Dysons-500M-failed-electric-car-revealed.html">Dyson’s electric cars project that lost £500m</a>, or the <a href="https://www.pressherald.com/2021/06/20/system-failure-inside-maines-35-million-human-resources-software-meltdown/">U.S. State of Maine’s $35m ERP disaster</a> or <a href="https://blog.360cloudsolutions.com/resources/top-six-erp-implementation-failures">Nike’s $400m ERP upgrade that cost them an extra $100m due to losses</a> are all examples of big institutions not being impervious to making project management mistakes. These failures are not new, but to what extent could losses be minimised if more explicit and intentional emphasis was placed on people, processes and technology?</p><p>What does any project mean without meaningful and even behavioural considerations for the people who handle the day-to-day project implementation? Does the tech stack have any credibility without efficient, ratified and well understood processes?</p><h3>People, Processes and Technology</h3><p>Technology is only as good as the people behind the processes who operate, maintain, and improve it. What this means is people, processes and technology are intertwined, interconnected and reliant upon each other:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RUzJAfmCzhXN63Xz" /></figure><p>According to a <a href="https://news.gallup.com/businessjournal/152429/cost-bad-project-management.aspx">Gallup report</a> technology projects fail because organisations place more energy and emphasis on “rational” factors (such as internal processes, hierarchies etc) rather than employee’s psychological engagement, the author mentions:</p><blockquote><em>Projects often fail because organizations put more emphasis on rational factors than on employees’ psychological engagement — and the cost to organizations is enormous</em></blockquote><p>This disconnect represents not only an opportunity cost of lost time and money, but also highlights a more worrying negative side effect: low morale and disengagement.</p><h3>Lack of Motivation</h3><p>Unmotivated workers are more likely to leave, more likely to be less productive, more likely to create a negative atmosphere and a host of other, difficult to resolve issues. Most candidly, no project can succeed in a negative and miserable atmosphere that induces stress and low morale.</p><p>Furthermore, when developing and delivering software solutions, morale must be kept high to medium for the duration of the engagement. When inevitable blockers and barriers do emerge, the team needs plenty in the reserve to galvanise itself and get through; without this, a project is in real danger of not being completed, a harsh reality many projects deal with.</p><h3>Communication Breakdown</h3><p>According to a <a href="https://www.business2community.com/strategy/project-management-statistics-45-stats-you-cant-ignore-02168819">Business 2 Community survey</a> updated in July 2022, the top five reasons IT projects fail:</p><ul><li>Change in organisations’ priorities — 39%</li><li>Change in project objectives — 37%</li><li>Inaccurate requirements gathering — 35%</li><li>Inadequate vision — 29%</li><li>Poor communication — 29%</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*to5yfgje8yMtD_4f" /></figure><p>A perceived change in direction, change in priorities and poor communication should be manageable with prioritising team members and stakeholders without them feeling disengaged and disillusioned. Participants in this survey clearly felt the barriers between management and the rest were strong enough to cite them for the primary reason(s) for project failures.</p><p>If you prioritise people relationships, transparent communication and genuine consideration it’s likely that many of those project failure reasons could be reduced.</p><h3>People Have to Buy In</h3><p>When an organisation embarks on digital transformation, whether that’s green or brownfield, nothing moves without people. People remain the conductors, components and conduits between processes and technology.</p><p><a href="https://www.geneca.com/why-up-to-75-of-software-projects-will-fail/">According to research from Geneca, 75%</a> of survey respondents admit failure on projects boiled down to a “lack of confidence,” citing projects that were “doomed from the start.” This suggests that there is a disconnect with the project goals and those implementing the project due to poor buy in from the SMEs and other stakeholders responsible for project implementation.</p><h3>Stakeholder Management</h3><p>Both internal and external stakeholder management is critical to successful technology implementations. Knowing who’s who, knowing how to deal with them, understanding their requirements, how to approach them and when with what and so on is of central importance. Stakeholders tend to fit into one of these categories:</p><ul><li>Partners</li><li>Suppliers</li><li>Regulators</li><li>Employees</li><li>Managers</li><li>Owners</li><li>Competitors</li><li>Customers</li></ul><p>Successful categorisation of all stakeholders is a good start and ongoing exercise because you immediately understand how the solution will affect them and their respective domain. Also, project failure could arise by misallocating resources in the direction of one stakeholder (or stakeholder type) at the expense of others. <a href="https://www.analystexchange.net/post/how-to-successfully-work-with-external-stakeholders-and-keep-them-happy">Here’s detailed breakdown of external stakeholder management.</a></p><p>Plotting and reshuffling all your stakeholders on a matrix like one below is a small yet powerful way to maintain control over your stakeholders. Plotting power vs level of attention quickly arranges people into manageable buckets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JmUvQ_JxrYfQsWFP" /></figure><p>Moreover, managing stakeholders remains central to successful solution delivery, yet it can be overlooked and taken for granted in the day-to-day real world. Mismanaging that vendor agreement or becoming too reliant on an external consultancy company are real examples of how projects ended up not being delivered on time and costing time and money.</p><h3>Sponsor Buy In</h3><p><a href="https://www.business2community.com/strategy/project-management-statistics-45-stats-you-cant-ignore-02168819">Inadequate sponsor support was cited for 26% of project failure according to Business 2 Community,</a> meaning over 1 in 4 projects fail due to lack of senior support.</p><p>When sponsors/decision makers are on board and engaged they tend to be some of the best allies when things do go wrong because trust has been cultivated due to prior and consistent inclusion. Therefore, include them at key milestones and throughout (where necessary) and you’ll gain their trust and respect along the way.</p><h3>Processes</h3><p>A process is a series of actions or steps taken to achieve a particular goal. Effective process design considers the impact of implementation to staff and customers, the skills required to successfully implement the solution, the requirements needed and a host of other behavioural, physiological, and professional considerations.</p><p><a href="https://www.pmi.org/-/media/pmi/documents/public/pdf/learning/thought-leadership/pulse/pmi-pulse-2020-final.pdf?v=2a5fedd3-671a-44e1-9582-c31001b37b61&amp;sc_lang_temp=en">According to a 2020 PMI report</a> 11.4% of investment is wasted due to inferior project management processes, the report suggests firms that fail to properly integrate project management into their strategies see their <a href="https://www.pmi.org/-/media/pmi/documents/public/pdf/learning/thought-leadership/pulse/pmi-pulse-2020-final.pdf?v=2a5fedd3-671a-44e1-9582-c31001b37b61&amp;sc_lang_temp=en">outright project failure rate by a factor of 2/3.</a></p><p>The strategic inclusion of a dedicated PMO/business analysis resource should effectively cover, with sufficient skill and rigour, the demands of effective process design. Carefully articulated and ratified process design/ business process modelling goes a long way to helping projects succeed as the data from PMI suggests.</p><p>Effective process design can be overlooked, and this is costly for many reasons. When embarking on a product build/project it’s critical to know the following:</p><ol><li>What processes do we need to solve the problem?</li><li>What are the key steps to achieve that?</li><li>What resources are we likely to need to achieve this?</li></ol><p>You won’t have all the answers at the start as this is when the least is known. It therefore makes sense to build iteratively so you learn as you build, <a href="https://www.linkedin.com/pulse/big-companies-still-fail-agile-bosa-igbinoba/">check this article out for why some large firms still struggle with agile methods.</a></p><p>A good high-level brainstorming session for example allows all key stakeholders to ratify and discuss potential solutions that will later go on to be detailed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*G0f012cIxbyxFYH3" /></figure><p>In truth, whatever style or method yields the best results, the best return, motivates and maintains high levels of morale is the methodology that should be used. It just happens that agile methods usually have a faster and higher ROI simply due to the principal of delivering working software sooner than waterfall as well as being able to accommodate change a lot easier than waterfall too.</p><p>According to a <a href="https://standishgroup.myshopify.com/collections/frontpage/products/project-resolution-benchmark">2020 Standish Group report</a> Agile projects were successful 42% of the time, whilst their waterfall counterparts only 13% of the time; a big disparity. The graph below also plots when projects were challenged (neither passed but not complete failures) and complete failures.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gnUOvYlbIQYNHF7X" /></figure><p>Moreover, astute process design, ratified and reviewed consistently will be assimilated into a product and then sprint backlog and will be developed within a transparent and adaptive environment rich with consistent levels of inspection and accountability from all involved.</p><p>Processes are therefore synonymous with those creating, implementing, ratifying and eventually deploying them, and this should reduce the failure rate, as the <a href="https://standishgroup.myshopify.com/collections/frontpage/products/project-resolution-benchmark">Standish Group report shows</a>. Expect greater levels of engagement and higher levels of scrutiny and a better environment for processing (inevitable) changes throughout the delivery lifecycle.</p><h3>Technology</h3><p>Technology should always be the final piece of the puzzle. Technology represents the proverbial “icing on the cake” simply because it has no worth without motivated people and efficient processes.</p><p>Project failure in relation to technology according to several studies, including a <a href="https://wellingtone.co.uk/wp-content/uploads/2020/06/The-State-of-Project-Management-Report-2020-Wellingtone.pdf">2020 study from Wellingtone that suggests 54% of surveyed participants</a> do not have the correct collaboration tools and technology for sufficient project management. Something as crucial as a collaboration tool boils down to not only the tool used (Jira, Azure Boards, VersionOne etc) but the personnel behind the tools, proper and effective setup, and astute people and process management as mentioned before.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*g2v8bWEmXyx0Fo42" /></figure><h3>Vendor Management</h3><p>In a 2022 court case in the UK, tech giant IBM was ordered by the Royal Courts of Justice to pay £80m ($105m) due to a failed implementation for UK insurer Co-Op insurance. Co-Op Insurance commissioned IBM for a £50m IT transformation project in 2015. IBM had the mandate to create a new underwriting system for the insurer. IBM were due to have made £125m to manage the system over the next 10 years, a £12.5m per year investment.</p><p>IBM had proposed to implement the transformation using agile methods as their preferred modus operandi, but Co-Op CEO Mark Summerfield lamented their use of agile, suggesting IBM’s implementation was “embarrassing,” saying the development method that was sold was “unproven” and “unworkable.” Summerfield went onto add:</p><blockquote><em>“With the benefit of hindsight, it is obvious to me that we were sold a product that did not exist (a UK capable version of Insurer Suite) and contracted against milestones that were very unlikely to be met.”</em></blockquote><p>A technology giant like IBM is not exempt from implementation disasters like this and this case proves that vendor selection and vendor management is a delicate and sensitive skill that requires careful management, realistic scoping, no or little disparity between RFP/sales pitch and the day-to-day implementation of the solution, a very common faux pas unfortunately, and closer relationships between internal and external stakeholders must be cultivated and maintained throughout the delivery lifecycle.</p><h3>Key Considerations</h3><ul><li>Was IBM’s agile approach not understood by Co-Op?</li><li>Were Co-Op not as well versed on the day-to-day of agile methods?</li><li>Why was the disparity between the sales and implementation teams so vast?</li></ul><p>Rhetorical questions at this point, but the points are valid: only being well versed with your people and processes can lead to a sound decision-making when it comes to technology selection, vendor management and other tech related issues; overlook this and it will cost time, money, effort, and even reputation damage in some cases.</p><h3>Conclusion</h3><p>Tech projects fail for a combination of reasons. Seldom is there one critical and overwhelming reason why a project has failed. In today’s article however, people, processes and technology has been outlined as the critical areas in which no project has any chance of success if these three critical areas are not properly managed.</p><p>All three are interlinked and have a critical dependency upon the other, remove, damage, or fail to maintain one component and all three fall apart and the project fails as a result. Pay attention, know and master one, then two, then all three, then your chances of project success increase dramatically.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5acbd4806721" width="1" height="1" alt=""><hr><p><a href="https://medium.com/agileinsider/the-cost-of-project-failure-people-processes-and-technology-5acbd4806721">The Cost of Project Failure — People, Processes and Technology</a> was originally published in <a href="https://medium.com/agileinsider">Agile Insider</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The A-Z of Product Management]]></title>
            <link>https://bosaigbinoba.medium.com/the-a-z-of-product-management-d9c3daf581bb?source=rss-905e40c4bee9------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9c3daf581bb</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Bosa Igbinoba]]></dc:creator>
            <pubDate>Tue, 17 Jan 2023 10:01:43 GMT</pubDate>
            <atom:updated>2023-01-17T10:01:43.751Z</atom:updated>
            <content:encoded><![CDATA[<p>Products need designing, building and managing. The best products add value and leave users delighted.</p><p>Some products are strictly functional and don’t require “delighted” users but must operate in an efficient and utility driven manner.</p><p>Whether it’s a productivity app designed to kill procrastination or an insurance app designed to give you a quote to help manage your risk or an app simply designed to kill time; all apps need effective and pragmatic product management.</p><p>Product Management isn’t new. In fact, where apps have been readily available there have been product managers. Yes, the role itself may be relatively new, but the functionality, responsibility and execution of effective product management is not new at all.</p><p>Despite this, the role of product manager has taken on a world of its own and now there’s plenty of resources out to help any newcomers to the field or seasoned vets, there’s plenty of information out there.</p><p>There’s actually a lot of crossover between product management and business analysis and many of the skills needed to be a good business analyst are welcomed in product management.</p><p>Basically, this list is a top to bottom look at the vast world of the concepts, ideas, methodologies, tools, and anything commonly associated with product management today.</p><p>Enjoy the list.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*kt-MB2FexwkLR1uD.jpeg" /></figure><p>Photo by <a href="https://unsplash.com/@jexo?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Jexo</a> on <a href="https://unsplash.com/s/photos/product-management?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></p><h3>A</h3><p><strong>is for Agile…</strong> This word is emotive, conjures mixed feelings depending on the audience, some lambast this concept, some adore it. Whatever your personal disposition, Agile’s impact on product management and software development is without question.</p><p>In a nutshell Agile places emphasis on delivering working software in a collaborative and transparent manner. Focused on working iteratively, Agile is a staple methodology of product management and any PM worth their salt is well versed with this developmental framework.</p><h3>B</h3><p><strong>is for Brainstorming… </strong>Whether you’re working solo, in a team or in groups, Brainstorming is an amazing, highly effective and natural way to process, analyze and convey information. Brainstorming is highly effective when starting from a high level, industry agnostic, easy to start and a great tool for product management for these reasons. Brainstorming brings order to chaos and still manages too not be rigid or too limiting. PMs love a good brainstorming session for a reason!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*uus72rac662xlQd1.jpeg" /></figure><p>Image by <a href="https://pixabay.com/users/fancycrave1-1115284/?utm_source=link-attribution&amp;utm_medium=referral&amp;utm_campaign=image&amp;utm_content=819371">fancycrave1</a> from <a href="https://pixabay.com/?utm_source=link-attribution&amp;utm_medium=referral&amp;utm_campaign=image&amp;utm_content=819371">Pixabay</a></p><h3>C</h3><p><strong>is for Customer… </strong>We could have easily gone for Cagan as in Marty Cagan here because Marty’s contribution to the world of product is second to none. Cagan also highlights the importance of understanding your customer when developing products. Working on a product with all the bells and whistles might receive praise and acclaim from critics, the media, stakeholders and so on, but if this solution does not translate into sales and positive feedback then your product/solution hasn’t solved any problems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*acsLzgbxkkNojZVS.jpeg" /></figure><p>Photo by <a href="https://unsplash.com/@charissek?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Charisse Kenion</a> on <a href="https://unsplash.com/s/photos/customers?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></p><p>For every iPod there’s a Zune (remember that?) for every VHS there’s Betamax, from Clubhouse to Google +… Customers usually have the last laugh, so don’t forget to incorporate them into product development otherwise you could spend precious time, energy and effort iterating and developing something that’s going to stay on the shelf.</p><h3>D</h3><p><strong>is for Design…</strong> Product, UX/UI and Web (Design) are just some of the skills, crafts and disciplines required to create a solution that enhances the product’s usability and this will add value to a customer’s life. Without careful and considerate design, within a cohesive team and environment, things quickly fall apart. A good PM knows how to keep the plates spinning!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*W1YSuWJTnh4C2Ing.jpeg" /></figure><p>Photo by <a href="https://unsplash.com/@aridley88?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Andrew Ridley</a> on <a href="https://unsplash.com/s/photos/design?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></p><p>A PM often operates at the intersection of Product, Web and UX/UI design and must steer decisions, ensure consistency and establish alignment across all design functions. Think of a PM like a Conductor and the different design elements as different parts of one orchestra. Remember this analogy as it may come in handy…</p><h3>E</h3><p><strong>is for Experiments…</strong> Experimentation is encouraged as much as it is expected in product management for several reasons. Without a willingness to try new things, methods and techniques you might fall short of meeting your customers’ needs and shipping products that actually delight. Experiments can go a very long way to helping product success.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*tS8akf75rIMD_yTr.jpeg" /></figure><p>Photo by <a href="https://unsplash.com/@girlwithredhat?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Girl with red hat</a> on <a href="https://unsplash.com/s/photos/experiment?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></p><p>Experiments within product management usually involve planning, implementation, monitoring and acting. Each phase is distinct and linear, but strategic and built upon the other. As these phases are quite self-explanatory, we won’t dive into detail here, but careful planning leads to smooth implementation, which leads to astute monitoring and a definitive set of rules and plans to act upon. Don’t be afraid to experiment with your product’s features!</p><h3>F</h3><p><strong>is for Features…</strong> Huge features, small features, features that never see the light of day, features that flop, features that provide the base of your solution; whatever it is, product management is the art and science of effective feature management, enhancement, implementation and deployment.</p><p>Features require stakeholder involvement, user/customer involvement and striking the balance between commercial success, budgetary discipline, robust design and efficient development. Yes, you’ve implemented and shipped an infinite scroll on one of your pages, but now your app is 10x slower than before… Making these tradeoffs and ensuring effective and productive testing of features is what separates the good PMs from the great PMs. There must be a sense of balance when looking after features and deciding what to work on next. Use your tools, support your team and get building.</p><h3>G</h3><p><strong>is for Growth Stage…</strong> At whatever phase of your business or product development, PMs and effective product management forms the basis of growth. Let’s face it, we all want to see what we work on grow.</p><p>In the typical product lifecycle, there are four distinct phases: Product Introduction, Growth, Maturity and Decline. During the growth phase you’re beginning to reap the benefits of product market fit, your sales rise, you start iterating the product to protect your brand and you’ve left behind some if not all of the copy-cats you came across at the start of this journey. Growth is the aim and quality PMs aim for this whether it’s for a feature, product or company.</p><h3>H</h3><p><strong>is for Human Centered Design (HCD)…</strong> Like UX, but not quite the same. The main and most noticeable difference stems from the notion that UX is widely considered a methodology whilst HCD is considered an overarching framework. Let’s explain the difference.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*IIsiIzHdVWTpi19M.jpeg" /></figure><p>Whilst the difference is subtle, UX is mainly task and deliverable based, think lo-fi/hi-fi wireframes, user personas and so on. HCD however, is more of a mindset that strides to guide thinking and focus when designing, iterating, testing and so on. Because design is generally blurry in terms of strict definitions comprehensive literature on HCD isn’t the easiest to find. But having an awareness of HCD as a PM will ensure more empathy in your work and creations and will enable you to relate to your customer a lot more.</p><h3>I</h3><p><strong>is for Iterate…</strong> Just keep going. As a PM it can feel like a never-ending hamster wheel. Many PMs work in a CI/CD environment, so after a deployment you’re straight back in with more to build and more to develop; it can be so intense!</p><p>‍</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*fKuqxmWJctZySxms.jpeg" /></figure><p>Photo by <a href="https://unsplash.com/@brett_jordan?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Brett Jordan</a> on <a href="https://unsplash.com/s/photos/iteration?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></p><p>‍</p><p>Therefore, being able to iterate a build is tantamount to product market fit and therefore success and your own personal health/wellbeing. Iterations are also the subject to methodologies such as Scrum, Lean, RAD, Agile and others. No matter the underlying framework, the ability to iterate product is the bread and butter of product management; whether you’re improving during those iterations is another subject all together but breaking down the complex is 100% essential. Use your iterations wisely.</p><h3>J</h3><p><strong>is for Jake Knapp…</strong> This was the last letter we found and a special thanks to Jake Knapp for the wonderful book titled “Sprint.” Ev Williams of Twitter and Medium suggests that you should <em>“read this book and do what it says if you want to build better products faster…”</em></p><p>What is wonderful for PMs in this essential text is relatable examples, actionable and applicable recommendations and the fact it’s written by folk who’ve earned their stripes within the technology/product world. Sprint is an essential text for aspiring and experienced PMs because at the very least acts as a great refresher on domain knowledge you’re likely to have if you’re more experienced and a clear and wonderful preliminary text if you’re a novice. Read this book. Check Jake’s profile by clicking <a href="https://jakek.medium.com/"><strong>here</strong></a><strong>.</strong></p><h3>K</h3><p><strong>is for Key Performance Indicators…</strong> KPIs are synonymous with many modern professions and product management is no different. When you need to keep a pulse on critical success factors for your product, understanding and utilizing a handful of the right KPIs can be the difference between good product management and great product management.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*RSadxpyC5XJM4eDX.jpeg" /></figure><p>Lukas from Pexels</p><p>Besides keeping you informed and ensuring product direction, KPIs can reassure your stakeholders too. You can use KPIs as justification for your next build or the basis of why you wish to reject an idea from a developer. Knowing how your product is performing keeps you ahead of the curve and will pay off once the correct information is fully assimilated. We could write an entire book on the criticality of understanding and using KPIs effectively, for now, ensure KPIs are close if not at the heart of your data-driven decision-making process.</p><h3>L</h3><p><strong>is for Lean…</strong> Continuous improvement and respect are the pillars in which Lean principals are built. Similar but not the same Agile, Lean attempts to reduce waste, inefficiencies in development and foster a culture of mutual respect within the professional environment.</p><p>Companies of all sizes often look for a silver bullet, whether it’s Agile, Scrum, Kanban or Lean. These theories face a plethora of difficulties during application in the real world and Lean is no different. In principle however, there’s a lot to gain from this methodology.</p><h3>M</h3><p><strong>is for Minimum Viable Product…</strong> A widely contested, highly emotive term within product development and management is the MVP. Attributed to Paul Graham for first coining the term during his time at Y-Combinator, MVP certainly still has a lot of use within product today. Yes, this term evokes a plethora of emotions, but the value in the concept is undeniable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*g8zimDwDDm3LV0KC.jpeg" /></figure><p>Photo by <a href="https://unsplash.com/@halacious?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">HalGatewood.com</a> on <a href="https://unsplash.com/collections/9928838/minimum-viable-product?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></p><p>Product market fit and high product uptake is essential to the success of your product. Developing and most crucially deploying an MVP allows you to move away from concept into market. Dealing with real customers with real feedback, generating or losing real money will make or break you and your team as a PM. Iterate quality and deploy with pace and an MVP in its truest sense does just that.</p><h3>N</h3><p><strong>is for Networking…</strong> “It’s who you know…” During this pandemic riddled world of late socializing has had to adapt to the pressures of lockdown living. Apps like Clubhouse have gatecrashed the staple of apps we tend to use and more than ever we feel compelled to network.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*O9vycqS7ypfJuof-.jpeg" /></figure><p>Photo by <a href="https://unsplash.com/@antenna?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Antenna</a> on <a href="https://unsplash.com/s/photos/networking?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></p><p>Long before the pandemic however most PMs understood and understand they are a conduit resource. Responsible for fostering alignment between technology and business, championing the product and its features, digesting customer/user feedback and so much more; all of this works better if you are comfortable networking and have high interpersonal awareness. This isn’t going out and sending hollow requests on LinkedIn, this is building meaningful relationships with the entities you come into contact with for your work. Without a strong network and excellent interpersonal skills, you’re pretty much toast and won’t last as a PM.</p><h3>O</h3><p><strong>is for Objectives…</strong> Being in a position of authority and responsibility empowers the typical PM. With all power is of course responsibility. Therefore, getting your product objectives correct is tantamount to your success.</p><p>Having clear, ordered objectives allows you to maintain control of the product regardless of where it is in its lifespan. This isn’t always easy. Yes, there are a plethora of apps/guides/materials out there that help you order your objectives, but it really boils down to a clear understanding of your business goals, your user/customer needs, resources available and your own personal wellbeing. These are broad, high level summaries, but they capture all the essential ingredients to understanding your objectives as a PM.</p><h3>P</h3><p><strong>is for Personas…</strong> The consolidation of archetypal descriptions of user behavior patterns in representational profiles, to humanize design focus is a Persona. By making characteristics and traits more realistic you can really drill down on your niche with effective and considerate personas. This will help create more empathy and increase your understanding of the problem you’re solving with the solution you’re making.</p><p>Personas not only aid design of a product solution, but they also help testing product too. If you don’t use personas, you’re in danger of creating a very broad, “bit of everything solution” that ironically solves nothing. A good PM understands the importance of carefully researched personas as this information can be used to help make better design decisions, which will probably lead to a better product.</p><h3>Q</h3><p><strong>is for Questionnaires…</strong> As a research method the questionnaire is highly valuable, relatively cheap to organize and operate and if deployed effectively, can be extremely useful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*WfoDlY40CNcAUKwn.jpeg" /></figure><p>Photo by <a href="https://www.pexels.com/@alex-green?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels"><strong>Alex Green</strong></a> from <a href="https://www.pexels.com/photo/crop-woman-reading-notes-on-clipboard-5699458/?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels"><strong>Pexels</strong></a></p><p>A good questionnaire collects carefully articulated information and can reveal priceless data in relation users/customers thoughts, characteristics, feelings, perceptions, behaviors, attitudes and so on. Again, a great PM understands how important it is to assimilate this information, turn the data into insights and steer decision making in a well-thought-out way. Questionnaires have been around for a very long time and still have a place in today’s data driven world.</p><h3>R</h3><p><strong>is for Roadmaps…</strong> This word conjures mixed feelings within the product world. Some are blasé and think there should be as little structure as possible as too many layers prohibit productivity and does not aid it. Others feel a stringent roadmap must be defined before anything gets done…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*yBz_eyDOgg65WWCP.jpeg" /></figure><p>Photo by <a href="https://unsplash.com/@esteejanssens?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Estée Janssens</a> on <a href="https://unsplash.com/s/photos/roadmap-planning?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></p><p>Naturally, a healthy blend of both is highly advised. A well designed, articulated and discussed roadmap provides the PM and the whole product team with a focal point. This clear vision promotes clarity, consistency and competence within a build, regardless of whatever stage the product is in. Whether you work at a true startup, scale-up or enterprise organization, product roadmaps are virtually essential if you wish to work and operate at an optimal level.</p><h3>S</h3><p><strong>is for Scrum…</strong> This entry was contentious. Having just completed Scrum Master training many myths were corrected/dismissed. Scrum as a methodology has transformed the professional workplace since it’s formulation in 1995. Not actually designed for software development, but heavily used within this domain, Scrum is a methodology used to solve complex problems.</p><p>The main artifacts of Scrum are Planning, Standups, Sprints and Retrospectives. A PM should be aware of this. Officially there is no “PM” within Scrum, only Product Owners, Scrum Masters and Developers. As a result, you might officially be a Product Owner if your organization elects to adopt Scrum.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*XnyE4lhXH_3c1big.jpeg" /></figure><p>Photo by <a href="https://www.pexels.com/@cottonbro?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels"><strong>cottonbro</strong></a> from <a href="https://www.pexels.com/photo/white-blue-and-yellow-sticky-notes-5990265/?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels"><strong>Pexels</strong></a></p><p>Implementing Scrum within organizations, mainly larger ones remains a challenge, due to the stringent nature of Scrum’s rules. The Scrum guide is an excellent resource and every PM should have read it at least once in their career. If you haven’t, you’ve got some reading to do straight after you’ve finished this!</p><h3>T</h3><p><strong>is for Testing…</strong> From smoke tests, to UAT, to sanity, to unit, to regression tests, to relatively obscure tests like MAT or monkey tests and all the other variations of tests in software and product development; testing is essential to product success.</p><p>Depending on where your team and you as a PM, without proper, effective, well documented, well-articulated and relevant tests, your product isn’t fit for purpose. You see, even with a well-tested product you can’t promise success, so without it, you may as well forget about releasing. Some PMs will actively get their hands dirty and test with the developers or even specialist testers, whilst others might oversee how things go, either way, an astute understanding of the different types of tests, when they should be used, why and what they are testing is essential.</p><h3>U</h3><p><strong>is for Users…</strong> Are users your bread and butter as a PM? Ponder this. There’s so much to be written for this one that keeping it brief was the real challenge…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*iYUaZ3rDFS_astxy.jpeg" /></figure><p>Photo by <a href="https://www.pexels.com/@kaboompics?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels"><strong>Kaboompics .com</strong></a> from <a href="https://www.pexels.com/photo/customers-users-color-wheel-6231/?utm_content=attributionCopyText&amp;utm_medium=referral&amp;utm_source=pexels"><strong>Pexels</strong></a></p><p>You see, there’s no crystal ball, nor silver bullet for pleasing users. Without pleasing them and keeping them onboard by consistently adding value and improving some aspect of their lives, they will take their attention elsewhere. Keep users engaged with a user friendly, valuable tool that solves their problem is at the heart of this profession. Keep this at the heart of your product management and you’ll do well.</p><h3>V</h3><p><strong>is for Value…</strong> Adding value is your job. Simple. Add value to your customers/users by taking regular stock with your clientele and removing their pain points over time through features and other tools at your disposal. We all use apps we deem valuable. The ones we love have a connection to us that’s deeper than a mere software/web application.</p><p>Adding value really does boil down to a simple before and after. What was my hour, day, week, year, life before I used this? If it is positive, you’re now a part of my life, if not, delete! Every good PM knows that they’re paid to find these windows and these opportunities they can capitalize on and ensure to add value and boost their product, app, feature and so on. Adding value is your job as a PM.</p><h3>W</h3><p><strong>is for Wireframes…</strong> It’s likely you’ll work with designers as a PM. Wireframing, once enough data and information has been gathered, analyzed, assimilated, and articulated is a step that comes soon after. Modern UX/UI breaks this process down into “low and high fidelity,” low being simple, black and white, conceptual and high being a working prototype that developers can actually play with prior to coding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*9tiL5i2KFBE0NQjP.jpeg" /></figure><p>Photo by <a href="https://unsplash.com/@sigmund?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Sigmund</a> on <a href="https://unsplash.com/s/photos/wireframes?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></p><p>Wireframes can also present great discussion points for all stakeholders as there is something for everyone to gather around and see. It’s amazing how quickly everybody turns into a designer all of a sudden! Still, wireframes done by a designer help you as a PM as they help turn ideas into something tangible and relatable and will accelerate your build and can even circumvent issues in the medium-long run. Wireframes work for any organization at any level of a product build.</p><h3>X</h3><p><strong>is for…</strong> X-factor! Easily the most challenging letter for this book! Releasing a product with simple, small quirks or “x-factor” can make a big difference. It’s worth a small risk taking a bit more development time and doing something for fun. It might not go down well or even be noticed, but if it does work that could be the difference between why your customers pick you over your rival. Think small and detailed, it isn’t always grand gestures that win. Small quirks when a page is loading or the cursor changing or some motion graphics on your website can be the x-factor your product has that makes it stick out vs its rivals. Sometimes, the small details go a long way.</p><h3>Y</h3><p><strong>is for YouTube…</strong> Clearly clutching at straws in terms of letters… The mammoth that is YouTube can teach us a lot about product, YouTube is the number one video search engine on the planet…</p><p>In terms of product management if we look at YouTube you can see how the platform has evolved over years. From a simple video hosting site to a full video search engine powered by the mighty Google. YouTube is on Smart TVs, iOS, Android and the classic webapp. Over years they have iterated, polished and expanded their product portfolio to attract new users and keep the old ones too. In terms of product trajectory, YouTube is one of the strongest case studies you can find.</p><h3>Z</h3><p><strong>is for John Zeratsky…</strong> John is a contributor to the PM bible that is “Sprint.” Besides that, Mr Zeratsky has a distinguished career within product, design and development. Working at YouTube, Google Ventures and writing for The Wall Street Journal, Zerasky understands the importance of productivity and how that helps fuel successful product builds. <a href="https://johnzeratsky.com/">Zeratsky’s site can be accessed right here</a></p><p>Here’s the list again:</p><p>A = Agile</p><p>B = Brainstorming</p><p>C = Customer</p><p>D = Design</p><p>E = Experiments</p><p>F = Features</p><p>G = Growth Stage</p><p>H = Human Centered Design (HCD)</p><p>I = Iterate</p><p>J = Jake Knapp</p><p>K = Key Performance Indicators (KPIs)</p><p>L = Lean</p><p>M = MVP</p><p>N = Networking</p><p>O = Objectives</p><p>P = Personas</p><p>Q = Quality Control/Assurance</p><p>R = Roadmaps/Requirements</p><p>S = Scrum</p><p>T = Testing</p><p>U = User</p><p>V = Value</p><p>W = Wireframes</p><p>X = X-Factor</p><p>Y = You Tube</p><p>Z = Zeratsky John</p><p>There is it. Your A-Z in Product Management! I hope you’ve enjoyed this. Thanks for reading.</p><p>‍</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9c3daf581bb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Start From Rock Bottom]]></title>
            <link>https://bosaigbinoba.medium.com/how-to-start-from-rock-bottom-1242f5fa5cec?source=rss-905e40c4bee9------2</link>
            <guid isPermaLink="false">https://medium.com/p/1242f5fa5cec</guid>
            <category><![CDATA[depression]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[self-care]]></category>
            <dc:creator><![CDATA[Bosa Igbinoba]]></dc:creator>
            <pubDate>Tue, 06 Sep 2022 08:53:05 GMT</pubDate>
            <atom:updated>2022-09-06T08:53:05.700Z</atom:updated>
            <content:encoded><![CDATA[<p>Whilst you’re in a storm it can feel like it’s never going to end; resist the self-pity trap and lift yourself up!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*77jEo_lHYlBSgX3CynHfHA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@anthonytran?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Anthony Tran</a> on <a href="https://unsplash.com/s/photos/depression?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Life is suffering.</p><p>Once you truly understand this life will make a lot more sense. Whilst fun can be had, love is experienced, we learn, we grow and feel and experience a plethora of emotions, the overarching theme and consistent, reoccurring characteristic of life is that every single human being walking God’s earth is here to suffer.</p><p>Naturally, you ask why…</p><p>That will be answered another time. For now, let’s focus on how to navigate whilst you’re dealing with a storm, major setback or just a consistent feeling of unhappiness, lack of purpose or lack of clear vision.</p><h3>Set Goals</h3><p>Prooper goal setting provides clarity, purpose, vision and aim. Meandering meaninglessly through life will compound and before you know it you’ve wasted some 3 years doing a lot of nothing.</p><p>Goals help us to focus our mind, our thoughts, our bodies, spirits and souls in a meaningful, productive and actionable way; set goals!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W-sM4swA74Z6QSa849DY_g.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@glamorousplanning?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Alexa Williams</a> on <a href="https://unsplash.com/s/photos/goals?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>SMART goals help make goals realistic and endow them with meaning and tangibility, so ensure you make them Specific, Measurable, Actionable, Relevant and Time-boxed.</p><h3>Take Action(s)</h3><p>A lack of action will open you up to the dangerous trap of self-pity. Self-pity is a cancer that must be destroyed at all costs.</p><p>Feeling sorry for one’s self is ugly, pointless and exacerbates the situation; simply ignore calls to feel sorry for the self.</p><p>This isn’t to say you shouldn’t mourn the death of a loved one, or take time to reflect ones’s past mistakes with the view of preventing the same mistakes again, nor contemplate your actions in a more reflective and purpose driven way.</p><p>But there’s a point where talking must stop and action must be taken. You’ll make mistakes along the way, you’ll mess up, but it beats wallowing in self-pity and inaction.</p><p>Don’t be too hard on yourself if you mess up, at least you’re making an effort and that’s better than nothing.</p><h3>Look After Yourself</h3><p>Healthy eating habits, exercise and ingesting positive stimuli are crucial when you’re down.</p><p>Avoid junk foods, processed sugars, meaningless content online and surround yourself with healthy and positive stimuli that encourages and motivates you to taking positive action(s).</p><p>The only way out is through and you must go through the storm in order to get through it. Life throws many curve balls, most of which we have no control over, so it’s how we deal with them that counts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ARPzCoHbxE8pNjFj_gs7xw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@littleforestowl?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Katrina Wright</a> on <a href="https://unsplash.com/s/photos/self-care?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Looking after yourself doens’t just mean eating well and watching and consuming great content, but reaching out to your friends when you need help, speaking up and sharing your feelings and seeking the presence of God when you truly need help are forms of self-care that will most likely be required when you’re going through the “mud” as it were.</p><h3>Seek The Presence of God</h3><p>As a Christian Jesus Christ is my personal Lord and Saviour, so I pray and read the Word regualrly.</p><p>I couldn’t advocate for any other spirtiual system as I came to Christ properly last year and spiritually, having practised just about all the alternative spiritual systems (transcedntial mediation, breathing exercises, “raising my consciousness level” etc.,) I can say from experience that nothing comes close to repentance for my personal sins and trusting in the Lord Jesus Christ.</p><p>When you come to Christ, your problems don’t disappear, but you have real support that is truly there in your life and I know this from personal experience. Salvation is free and God would welcome you if you’re willing to be humble and accept that you’ve broken his laws — something we’ve all done as humans.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rt1T_dbcOQG16o9vrVjKKQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@memphismonroe?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Memphis Monroe</a> on <a href="https://unsplash.com/s/photos/jesus-christ?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>The truth is, there are ways round feeling like you’re at rock bottom, but without a real and tangible relationship with God these issues will just keep coming back. You can pave over them with money or carnal pleasures, but that true peace of heart will evade you with a real relationship with God.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1242f5fa5cec" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Modelling Business Processes can boost your UI/UX career]]></title>
            <link>https://medium.com/design-bootcamp/modelling-business-processes-can-boost-your-ui-ux-career-e7437ae61c0b?source=rss-905e40c4bee9------2</link>
            <guid isPermaLink="false">https://medium.com/p/e7437ae61c0b</guid>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Bosa Igbinoba]]></dc:creator>
            <pubDate>Mon, 22 Aug 2022 08:32:58 GMT</pubDate>
            <atom:updated>2022-08-22T08:32:58.626Z</atom:updated>
            <content:encoded><![CDATA[<p>Performing user research is crucial to successful design and modelling business processes at the start of your design journey may add new tools to your analytical arsenal as a Designer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZkhCKYogyzK1iNE374fJ4A.jpeg" /></figure><p>This relatively simple task can boost your understanding of business and user pain points at the start of the design process, save valuable time and effort over the duration of your project and help maintain focus on the outcome needed from both user and business respectively.</p><p>The creation, gathering and documentation of business requirements is central to great UI and UX. In today’s case, we’ll focus on UX. Of course, the two are intertwined but for an enhanced, optimal and successful user experience, the UI/UX Designer,</p><p>Product Designer, business and any other key stakeholder must acknowledge that a clear, coherent understanding of business processes is central to the successful implementation of optimal UX; even if this step was never explicitly acknowledged. Therefore, a good understanding of business processes could boost your UI/UX career, both short and long-term.</p><p>According to the <a href="https://www.coursera.org/learn/user-experience-design/home/welcome">Georgia Institute of Technology </a>the four common phases of UI/UX design are:</p><p><em>1. Requirements Gathering</em></p><p><em>2. Design Alternatives</em></p><p><em>3. Prototyping (low and high fidelity)</em></p><p><em>4. Evaluation</em></p><p>Each of these phases is of course a vast realm in and of themselves. For today we will focus on number one. It is in this phase as Designers, we understand the user and the business and what their goals are.</p><p>We also understand the current practices of both, the “problem space” and most crucially we present tools and techniques that allow the user and/or the business to explain their issues. It is in this last step in particular, the mapping and documentation of business processes lends the most value.</p><p>The assimilation of this information is the bedrock in which a successful UX solution can be built. Your aim as a Designer is to ensure the end user at the end of the process is delighted with the solution you have created. Therefore:</p><blockquote>You must have the analytical tools to be able to translate the user and or the businesses needs into simple, clear, well-structured models and business process models are a great way to begin.</blockquote><p>Before we go further, lets explain business processes and business models in a bit more depth.</p><h3>What Are Business Processes?</h3><p>Business processes are the methods in which an organization conducts internal operations and delivers its products and services to its customers. Some reasons for creating business process models include:</p><p>· <strong>Understanding how the current processes work</strong>: A Designer can be brought into a situation that requires transformation or rebranding. Illustrating the current or “As-Is” process illustrates this.</p><p>·<strong> To establish consistency:</strong> If an organization has too many disparate processes, alignment and consistency may be an aim. Consolidating various processes into a single or a few streamlined practices or processes may need to be mapped.</p><p>·<strong> Identifying strengths and weaknesses:</strong> The ability to identify strengths and weaknesses within a current process allows a business to allocate sufficient resources accordingly, this stems from an accurate description/depiction of business processes.</p><h3>Business Process Models</h3><p>Being able to model processes, journeys and flows allows the necessary information to be communicated diagrammatically, a picture speaks a thousand words for a reason. Once we see how something works it can help us understand the process quicker as opposed to writing the process down in tabular or linear form.</p><p>A typical business process consists of five key aspects:</p><p><em>1. Tasks that make up the process</em></p><p><em>2. Process Flows</em></p><p><em>3. Decision Points</em></p><p><em>4. Actors</em></p><p><em>5. Outcomes</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WJlzMN3BdKB-5-29.jpeg" /></figure><p>A Process Flow captures a lot of info in a tight structure</p><p>This process outlines the necessary steps for a customer to call a taxi. The Actors are represented via aspects we refer to as ‘swimlanes.’ Each swimlane represents an individual interest. There is one start point in which the journey starts, various tasks or processes and a single end point. A process-flow can contain multiple end points based on what is being modelled, but there should only be one point of origin.</p><p>In terms of UX, having a clear outline <strong><em>before</em></strong><em> </em>prototyping will enhance clarity between business and designer because the important processes are outlined from the outset.</p><p>In the example above, the Designer knows who the main players are, knows how and when they interact with each other, potential pain points (wait icon in customer swimlane) and has a high-level sequence of events depicted. All this information deduced from a simple process flow.</p><p>It’s surprising how little this practice is adopted in the world of UI/UX and design in general.</p><h3>Prototyping</h3><p>Modelling business processes via a standard BPMN (Business Process Model Notation) process flow will enhance your prototyping experience, often making the process much more efficient and accurate from the start; thus saving valuable time and resources and will help you reach high-fidelity protypes much quicker than before.</p><p>Whilst working on a complex build as a Business Analyst, I decided to equip the UI/UX Designer with a series of process flows at the start. Doing this <em>prior </em>to prototyping tremendously enhanced the Designer because there was a clear sequence of both user and business needs clearly expressed in a systematic and structured manner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SqzocAG8U19AK_n1.jpeg" /></figure><p>Photo by <a href="https://unsplash.com/@alvarordesign?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Alvaro Reyes</a> on <a href="https://unsplash.com/s/photos/ux-ui?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></p><p>Capturing processes via a process flow is a step that is surprisingly understated and undervalued and is not really seen as an accepted part of the prototyping process within the UI/UX world.</p><p>Of course, there’s no complete set of rules to doing anything, especially in the vast world of UI/UX design. However, certain fundamentals are and have become industry standard and if Prototyping is a firm and accepted step in UI/UX design, then modelling business/customer processes could be a welcome addendum to this crucial step.</p><p>Business process flows also embrace full discussion from the whole team, from Product Managers, Business Analysts, Designers, Product Owners, Stakeholders and more; each with a unique stake in the product/project outcome.</p><h3>Customer Process Modelling</h3><p>Business process maps/models are not designed or intended to remove the user from the experience or replace a standard customer flow.</p><p>This is not the case at all. The name does suggest a focus on business as opposed to user, but the models are only in relation to servicing the end customer. The focus is very much on the user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ESohXgvMO6K8bHEK.jpeg" /></figure><p>Business process models can support customer journey maps not replace them</p><p>Process models allow all relevant stakeholders to understand how their good or service reaches the end customer and this information allows Designers and the business to have a consistent focal point throughout the build, whether it’s Prototyping, High-Fidelity mock-ups, Testing or presenting the finished design; using the process models throughout the design will enhance your understanding of what your client wants, what your user wants and help to maintain focus.</p><p>Successful design has been achieved for years without incorporating new techniques, but marginal differences to workflow, work habits and best practices are sought after by so many, just read Producthunt for the latest “productivity-hack” or “efficiency tool.”</p><p>Embracing business process models is simple and a relatively understated method in which a lot of value can be derived throughout the design process without that much work done upfront.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*n0OS1PJFeogrJNcI.jpeg" /></figure><p>Photo by <a href="https://unsplash.com/@youxventures?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">You X Ventures</a> on <a href="https://unsplash.com/s/photos/product-management?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></p><p>Most projects/product teams have Business Analysts, Product Managers, Project Managers, Requirements Engineers or other specialists whose focus is on understanding, challenging and Analyzing current practices and creating ways in which to optimize this.</p><p>Utilizing this existing tool could be a subtle enhancement to your workflow as a Designer and the effects could have huge positive implications for your end-user, clients and your personal work as a Designer.</p><p>Start your next design project with mapping business processes and see what a difference it makes to the outcome for both you your client and the end user.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7437ae61c0b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/modelling-business-processes-can-boost-your-ui-ux-career-e7437ae61c0b">Modelling Business Processes can boost your UI/UX career</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tesla Operates Agile on Scale and its Car Insurance Product is Proof]]></title>
            <link>https://medium.com/agileinsider/tesla-operates-agile-on-scale-and-its-car-insurance-product-is-proof-91a50fe8bf12?source=rss-905e40c4bee9------2</link>
            <guid isPermaLink="false">https://medium.com/p/91a50fe8bf12</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[elon-musk]]></category>
            <category><![CDATA[insurance]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[tesla]]></category>
            <dc:creator><![CDATA[Bosa Igbinoba]]></dc:creator>
            <pubDate>Tue, 16 Aug 2022 11:53:12 GMT</pubDate>
            <atom:updated>2022-08-16T11:53:12.368Z</atom:updated>
            <content:encoded><![CDATA[<p>The term ‘disruption’ is thrown about a lot. It implies existing systems, industries, practices, and the general status quo has been rearranged, changed or has been forced to rethink certain standards, behaviours, and practices. If ever there was a company that embodies the ethos of disruption, it’s Tesla.</p><p>Tesla is a famous example of a company that symbolises industry disruption, not only the way the company is transforming the motor industry, but the insurance industry too. You know what the underlying blueprint of Tesla’s disruption is? Agile.</p><p>Tesla is an example of what happens when business agility is given full support from those who have influence, given enough time to grow and compound and is supported by those on the ground doing the heavy lifting.</p><p>Today’s article is a focus on how ‘agile’ is at the heart of business operations on both the manufacturing and culture side, as well as how Tesla sells motor insurance.</p><h3>Individuals and Interactions</h3><p>When we break the agile manifesto down line by line we can pinpoint where, explicitly, or implicitly Tesla motors have applied the principles:</p><blockquote>“Individuals and interactions over processes and tools”</blockquote><p>It’s known within Tesla that design and engineers sit together. This coherent bond between both teams eradicates the idea of separation and silos, the result, a seamless blend between two usually disparate teams.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*qd8y8s-ljtg4afsm" /></figure><p>Tesla clearly focus on two major areas: the product and the people. The ‘people’ being both the customer and the staff. Musk tends to hire and retain passionate people for all his companies, <a href="https://www.quora.com/What-is-it-like-to-work-with-for-Elon-Musk">as this SpaceX employee attests</a>.</p><p>Moreover, Tesla harnesses the power of cross-functional teams, where design and engineering sitting together is a simple, almost nondescript example, yet it highlights agile in motion and the results prove there is some method to the madness.</p><h3>Closer Customer Collaboration</h3><blockquote>“Customer collaboration over contract negotiation.”</blockquote><p>There is a substantial push to move away from petrochemical or traditional engines and a move towards alternatives, namely electric energy that has gathered significant support over the last 20 years.</p><p>This piece isn’t here to lament petrol/diesel, more, to reflect the fact that the environment and the perception of electricity being better for the world is a voice growing louder and louder each year. Musk has said:</p><blockquote>“It’s very important to have a feedback loop, where you’re constantly thinking about what you’ve done and how you could be doing it better.”</blockquote><p>This mainly tacit but sometimes deliberate collaboration between Tesla, their customers and “the world” epitomises the agile principal of “Customer collaboration over contract negotiation.”</p><p>Musk is also describing a Scrum Retrospective, a ceremony in which the team reflect and contemplate ways to make improvements on the previous sprint.</p><p>The feedback loop Musk is referring to suggests customer feedback is ingrained into the Tesla ethos. Tesla appear to have an environment in which assimilating feedback and acting on it is possible without losing too much developmental momentum.</p><h3>Working Software</h3><blockquote>“Working software over comprehensive documentation”</blockquote><p>The fact that Tesla cars automatically update the in-car firmware on a regular basis highlights Tesla’s business agility. Without a Continuous Integration/ Continuous Development (CI/CD) environment this wouldn’t be possible.</p><p>So, much like a smart phone that has regular updates to ensure optimal performance, Tesla cars also ensure its drivers are operating with the latest firmware.</p><h3>Tesla Car Insurance</h3><p>Tesla’s business agility has enabled them to break into an industry that has insurmountable barriers to entry from the insurance carrier perspective.</p><p>The car insurance industry consists of a few large firms (at carrier level) and without business agility from the very top Tesla would not have had a chance to break into this large market.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*utXmy9_HIXQOLL1w" /></figure><h3>Not a Direct Rival to Existing Insurers</h3><p>Admittedly, Tesla’s insurance product is exclusive to Tesla car owners, so it’s not a traditional motor insurer from that perspective.</p><p>Also, Tesla’s motor insurance product is more of a complementary/add-on good attached to the sale of their cars.</p><p>Feasibly, they could have entered a joint venture with an existing carrier but felt it would be optimal for the customer to underwrite its own risks, cutting out brokers, carriers and maybe reinsurers in the process.</p><h3>Musk’s Opinion on Motor Insurance</h3><p>Musk has been vocal on the perceived inefficiencies within motor insurance:</p><blockquote>“The car insurance industry is incredibly inefficient.”</blockquote><p>Musk <a href="https://youtu.be/CnxzrX9tNoc?t=1195">told attendees</a> of the All-In Summit in Miami.</p><blockquote>“You’ve got so many middle entities, from insurance agents all the way to the final reinsurer, there’s like a half-dozen companies each taking a cut.”</blockquote><p>By cutting out other entities from the value offering and going direct to customer, Tesla could be setting up a new, holistic insurance product that could disrupt the existing market.</p><p>For now, it’s too early to see what this model of car purchase and direct insurance does, but some insurers have taken notice already.</p><h3>Value Offering</h3><p>Tesla aims to transform the motor insurance by doing the following:</p><ul><li>Leverage onboard real-time driver behaviour to calculate bespoke premiums</li><li>Automated monthly premium collection</li></ul><p>There’s nothing revolutionary here and a telematics or ‘little black box’ installed can yield similar results.</p><p>Although, Tesla’s superior data collection devices should collect far more sophisticated and accurate driver behaviour data.</p><p>This could facilitate granular and truly bespoke rating factors and could also provide an impression of the driver other insurance companies cannot compete with.</p><p>Because of Tesla’s onboard real-time advanced data collection abilities, premiums should be a lot more competitive than a standard insurer due to the superior data collection. Existing insurers simply can’t compete with that level of data granularity.</p><h3>What Does This Mean for Motor Insurance?</h3><ul><li>Are more accurate premiums enough to persuade drivers to shift to driving a Tesla?</li><li>Will other electric car manufacturers copy the Tesla motor insurance model?</li><li>What does this mean for motor insurance going forward?</li></ul><p><a href="https://www.swissre.com/media/press-release/nr-20201012-swiss-re-and-daimler-launch-movinx-to-transform-automotive-mobility-insurance-business.html">Reinsurance giant Swiss Re has partnered with motor giant Daimler</a>, maybe in an anticipatory move to ‘future-proof’ itself against the move away from petrol/diesel into electricity.</p><p>Will we see more insurance and car manufacturer collaborations? One thing is clear, Tesla has capitalised on its superior data collection by transforming it into an additional revenue avenue in the form of car insurance.</p><h3>Traditional Insurers Struggle with Data</h3><p>Many insurers struggle to fully harness the power and potential of data and analytics within insurance.</p><p>Many carriers know there’s untapped potential waiting to enhance underwriting and claims processes, but a plethora of legacy system-integration issues and a lack of true business agility are amongst several other issues preventing insurers from becoming big-data powerhouses.</p><p>This means data adoption and utilisation isn’t a straight-forward reality for many insurers; for Tesla, this isn’t the case.</p><p><a href="https://insuranceblog.accenture.com/heres-why-insurers-struggle-to-get-value-from-their-data">According to a 2020 report from Accenture</a> 88% of participants have little idea on how to harness the power of the data they own. <a href="https://www.linkedin.com/in/jean-francois-gasc-1932791b/">Jean-François Gasc</a>, the report author suggests:</p><blockquote>Insurers are fast realizing that their data is a critical asset that can give them a big edge on their competitors. But many carriers struggle to unlock the value trapped in their data. Our research shows that big companies only analyse 12 percent of their data. A staggering 88 percent of corporate data is sitting idle.</blockquote><p>Performance related premiums are likely to incentivise greater levels of caution for Tesla owners who have a direct benefit for being more considered whilst driving.</p><p>This is already done with “little black boxes” installed by some car insurers, but Tesla’s offering is substantially more sophisticated than anything else on the market.</p><h3>Conclusion</h3><p>What Tesla’s business agility and car insurance proposition has done has made traditional car manufacturers like Porsche rethink how it sells insurance.</p><p><a href="https://www.munichre.com/en/company/media-relations/media-information-and-corporate-news/media-information/2020/flexfactory.html">This 2020 partnership with reinsurance giant Munich Re</a> suggests car manufactures and insurance companies could form closer partnerships as the industry has been forced to rethink.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1Juah6z_4o2eF91J" /></figure><p>Tesla probably haven’t forced the entire industry to rethink despite the media hyperbole, however, they do seem to have at least operated as an inspired catalyst that has at least constructed newer partnerships and conversations.</p><p>Despite only being roughly 2% of cars on the road in the UK, Tesla’s approach to car manufacturing and car insurance has made more traditional companies, both car manufacturers and insurance companies alike stand-up and take notice, and this could not have taken place without Tesla embracing and then scaling agile practices and principles.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=91a50fe8bf12" width="1" height="1" alt=""><hr><p><a href="https://medium.com/agileinsider/tesla-operates-agile-on-scale-and-its-car-insurance-product-is-proof-91a50fe8bf12">Tesla Operates Agile on Scale and its Car Insurance Product is Proof</a> was originally published in <a href="https://medium.com/agileinsider">Agile Insider</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Cost of Project Failure — People, Processes and Technology]]></title>
            <link>https://medium.com/design-bootcamp/the-cost-of-project-failure-people-processes-and-technology-fe8473a1f34d?source=rss-905e40c4bee9------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe8473a1f34d</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Bosa Igbinoba]]></dc:creator>
            <pubDate>Thu, 11 Aug 2022 13:47:01 GMT</pubDate>
            <atom:updated>2022-08-13T10:32:45.767Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Cost of Project Failure — People, Processes and Technology</h3><p>Technology projects are industry agnostic, affect billions of people and are still rife with inefficiencies that lead to so many of them failing.</p><p>Failure usually costs valuable time, money, effort, and other resources that are difficult or impossible to recoup.</p><p>Failed projects, ranging from <a href="https://www.thisismoney.co.uk/money/cars/article-8380881/New-images-Dysons-500M-failed-electric-car-revealed.html">Dyson’s electric cars project that lost £500m</a>, or the <a href="https://www.pressherald.com/2021/06/20/system-failure-inside-maines-35-million-human-resources-software-meltdown/">U.S. State of Maine’s $35m ERP disaster</a> or <a href="https://blog.360cloudsolutions.com/resources/top-six-erp-implementation-failures">Nike’s $400m ERP upgrade that cost them an extra $100m due to losses</a> are all examples of big institutions not being impervious to making project management mistakes.</p><p>These failures are not new, but to what extent could losses be minimised if more explicit and intentional emphasis was placed on people, processes and technology?</p><p>What does any project mean without meaningful and even behavioural considerations for the people who handle the day-to-day project implementation? Does the tech stack have any credibility without efficient, ratified and well understood processes?</p><h3>People, Processes and Technology</h3><p>Technology is only as good as the people behind the processes who operate, maintain, and improve it. What this means is people, processes and technology are intertwined, interconnected and reliant upon each other:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2wf_ZzMEwjlUeXPj" /></figure><p>According to a <a href="https://news.gallup.com/businessjournal/152429/cost-bad-project-management.aspx">Gallup report</a> technology projects fail because organisations place more energy and emphasis on “rational” factors (such as internal processes, hierarchies etc) rather than employee’s psychological engagement, the author mentions:</p><blockquote><em>Projects often fail because organizations put more emphasis on rational factors than on employees’ psychological engagement — and the cost to organizations is enormous</em></blockquote><p>This disconnect represents not only an opportunity cost of lost time and money, but also highlights a more worrying negative side effect: low morale and disengagement.</p><h3>Lack of Motivation</h3><p>Unmotivated workers are more likely to leave, more likely to be less productive, more likely to create a negative atmosphere and a host of other, difficult to resolve issues.</p><p>Most candidly, no project can succeed in a negative and miserable atmosphere that induces stress and low morale.</p><p>Furthermore, when developing and delivering software solutions, morale must be kept high to medium for the duration of the engagement.</p><p>When inevitable blockers and barriers do emerge, the team needs plenty in the reserve to galvanise itself and get through; without this, a project is in real danger of not being completed, a harsh reality many projects deal with.</p><h3>Communication Breakdown</h3><p>According to a <a href="https://www.business2community.com/strategy/project-management-statistics-45-stats-you-cant-ignore-02168819">Business 2 Community survey</a> updated in July 2022, the top five reasons IT projects fail:</p><ul><li>Change in organisations’ priorities — 39%</li><li>Change in project objectives — 37%</li><li>Inaccurate requirements gathering — 35%</li><li>Inadequate vision — 29%</li><li>Poor communication — 29%</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0xFR4sUEbdPAB-pi" /></figure><p>A perceived change in direction, change in priorities and poor communication should be manageable with prioritising team members and stakeholders without them feeling disengaged and disillusioned.</p><p>Participants in this survey clearly felt the barriers between management and the rest were strong enough to cite them for the primary reason(s) for project failures.</p><p>If you prioritise people relationships, transparent communication and genuine consideration it’s likely that many of those project failure reasons could be reduced.</p><h3>People Have to Buy In</h3><p>When an organisation embarks on digital transformation, whether that’s green or brownfield, nothing moves without people. People remain the conductors, components and conduits between processes and technology.</p><p><a href="https://www.geneca.com/why-up-to-75-of-software-projects-will-fail/">According to research from Geneca, 75%</a> of survey respondents admit failure on projects boiled down to a <em>“lack of confidence,”</em> citing projects that were <em>“doomed from the start.”</em> This suggests that there is a disconnect with the project goals and those implementing the project due to poor buy in from the SMEs and other stakeholders responsible for project implementation.</p><h3>Stakeholder Management</h3><p>Both internal and external stakeholder management is critical to successful technology implementations. Knowing who’s who, knowing how to deal with them, understanding their requirements, how to approach them and when with what and so on is of central importance. Stakeholders tend to fit into one of these categories:</p><ul><li>Partners</li><li>Suppliers</li><li>Regulators</li><li>Employees</li><li>Managers</li><li>Owners</li><li>Competitors</li><li>Customers</li></ul><p>Successful categorisation of all stakeholders is a good start and ongoing exercise because you immediately understand how the solution will affect them and their respective domain.</p><p>Also, project failure could arise by misallocating resources in the direction of one stakeholder (or stakeholder type) at the expense of others. <a href="https://www.analystexchange.net/post/how-to-successfully-work-with-external-stakeholders-and-keep-them-happy">Here’s detailed breakdown of external stakeholder management.</a></p><p>Plotting and reshuffling all your stakeholders on a matrix like one below is a small yet powerful way to maintain control over your stakeholders. Plotting power vs level of attention quickly arranges people into manageable buckets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jDSQJ5LY41HblNZ8" /></figure><p>Moreover, managing stakeholders remains central to successful solution delivery, yet it can be overlooked and taken for granted in the day-to-day real world.</p><p>Mismanaging that vendor agreement or becoming too reliant on an external consultancy company are real examples of how projects ended up not being delivered on time and costing time and money.</p><h3>Sponsor Buy In</h3><p><a href="https://www.business2community.com/strategy/project-management-statistics-45-stats-you-cant-ignore-02168819">Inadequate sponsor support was cited for 26% of project failure according to Business 2 Community,</a> meaning over 1 in 4 projects fail due to lack of senior support.</p><p>When sponsors/decision makers are on board and engaged they tend to be some of the best allies when things do go wrong because trust has been cultivated due to prior and consistent inclusion.</p><p>Therefore, include them at key milestones and throughout (where necessary) and you’ll gain their trust and respect along the way.</p><h3>Processes</h3><p>A process is a series of actions or steps taken to achieve a particular goal. Effective process design considers the impact of implementation to staff and customers, the skills required to successfully implement the solution, the requirements needed and a host of other behavioural, physiological, and professional considerations.</p><p><a href="https://www.pmi.org/-/media/pmi/documents/public/pdf/learning/thought-leadership/pulse/pmi-pulse-2020-final.pdf?v=2a5fedd3-671a-44e1-9582-c31001b37b61&amp;sc_lang_temp=en">According to a 2020 PMI report</a> 11.4% of investment is wasted due to inferior project management processes, the report suggests firms that fail to properly integrate project management into their strategies see their <a href="https://www.pmi.org/-/media/pmi/documents/public/pdf/learning/thought-leadership/pulse/pmi-pulse-2020-final.pdf?v=2a5fedd3-671a-44e1-9582-c31001b37b61&amp;sc_lang_temp=en">outright project failure rate by a factor of 2/3.</a></p><p>The strategic inclusion of a dedicated PMO/business analysis resource should effectively cover, with sufficient skill and rigour, the demands of effective process design.</p><p>Carefully articulated and ratified process design/ business process modelling goes a long way to helping projects succeed as the data from PMI suggests.</p><p>Effective process design can be overlooked, and this is costly for many reasons. When embarking on a product build/project it’s critical to know the following:</p><ol><li>What processes do we need to solve the problem?</li><li>What are the key steps to achieve that?</li><li>What resources are we likely to need to achieve this?</li></ol><p>You won’t have all the answers at the start as this is when the least is known. It therefore makes sense to build iteratively so you learn as you build, <a href="https://www.linkedin.com/pulse/big-companies-still-fail-agile-bosa-igbinoba/">check this article out for why some large firms still struggle with agile methods.</a></p><p>A good high-level brainstorming session for example allows all key stakeholders to ratify and discuss potential solutions that will later go on to be detailed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*R0cmUqgHXTTzgUJi" /></figure><p>In truth, whatever style or method yields the best results, the best return, motivates and maintains high levels of morale is the methodology that should be used.</p><p>It just happens that agile methods usually have a faster and higher ROI simply due to the principal of delivering working software sooner than waterfall as well as being able to accommodate change a lot easier than waterfall too.</p><p>According to a <a href="https://standishgroup.myshopify.com/collections/frontpage/products/project-resolution-benchmark">2020 Standish Group report</a> Agile projects were successful 42% of the time, whilst their waterfall counterparts only 13% of the time; a big disparity. The graph below also plots when projects were challenged (neither passed but not complete failures) and complete failures.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5Xv07zJMpg1bNDlZ5WnQeg.png" /></figure><p>Moreover, astute process design, ratified and reviewed consistently will be assimilated into a product and then sprint backlog and will be developed within a transparent and adaptive environment rich with consistent levels of inspection and accountability from all involved.</p><p>Processes are therefore synonymous with those creating, implementing, ratifying and eventually deploying them, and this should reduce the failure rate, as the <a href="https://standishgroup.myshopify.com/collections/frontpage/products/project-resolution-benchmark">Standish Group report shows</a>.</p><p>Expect greater levels of engagement and higher levels of scrutiny and a better environment for processing (inevitable) changes throughout the delivery lifecycle.</p><h3>Technology</h3><p>Technology should always be the final piece of the puzzle. Technology represents the proverbial “icing on the cake” simply because it has no worth without motivated people and efficient processes.</p><p>Project failure in relation to technology according to several studies, including a <a href="https://wellingtone.co.uk/wp-content/uploads/2020/06/The-State-of-Project-Management-Report-2020-Wellingtone.pdf">2020 study from Wellingtone that suggests 54% of surveyed participants</a> do not have the correct collaboration tools and technology for sufficient project management.</p><p>Something as crucial as a collaboration tool boils down to not only the tool used (Jira, Azure Boards, VersionOne etc) but the personnel behind the tools, proper and effective setup, and astute people and process management as mentioned before.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fQ6dqosf1k3_1blD" /></figure><h3>Vendor Management</h3><p>In a 2022 court case in the UK, tech giant IBM was ordered by the Royal Courts of Justice to pay £80m ($105m) due to a failed implementation for UK insurer Co-Op insurance. Co-Op Insurance commissioned IBM for a £50m IT transformation project in 2015.</p><p>IBM had the mandate to create a new underwriting system for the insurer. IBM were due to have made £125m to manage the system over the next 10 years, a £12.5m per year investment.</p><p>IBM had proposed to implement the transformation using agile methods as their preferred modus operandi, but Co-Op CEO Mark Summerfield lamented their use of agile, suggesting IBM’s implementation was <em>“embarrassing,” </em>saying the development method that was sold was “unproven” and <em>“unworkable.”</em> Summerfield went onto add:</p><blockquote>“With the benefit of hindsight, it is obvious to me that we were sold a product that did not exist (a UK capable version of Insurer Suite) and contracted against milestones that were very unlikely to be met.”</blockquote><p>A technology giant like IBM is not exempt from implementation disasters like this and this case proves that vendor selection and vendor management is a delicate and sensitive skill that requires careful management, realistic scoping, no or little disparity between RFP/sales pitch and the day-to-day implementation of the solution, a very common faux pas unfortunately, and closer relationships between internal and external stakeholders must be cultivated and maintained throughout the delivery lifecycle.</p><h3>Key Considerations</h3><ul><li>Was IBM’s agile approach not understood by Co-Op?</li><li>Were Co-Op not as well versed on the day-to-day of agile methods?</li><li>Why was the disparity between the sales and implementation teams so vast?</li></ul><p>Rhetorical questions at this point, but the points are valid: only being well versed with your people and processes can lead to a sound decision-making when it comes to technology selection, vendor management and other tech related issues; overlook this and it will cost time, money, effort, and even reputation damage in some cases.</p><h3>Conclusion</h3><p>Tech projects fail for a combination of reasons. Seldom is there one critical and overwhelming reason why a project has failed.</p><p>In today’s article however, people, processes and technology has been outlined as the critical areas in which no project has any chance of success if these three critical areas are not properly managed.</p><p>All three are interlinked and have a critical dependency upon the other, remove, damage, or fail to maintain one component and all three fall apart and the project fails as a result.</p><p>Pay attention, know and master one, then two, then all three, then your chances of project success increase dramatically.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe8473a1f34d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-cost-of-project-failure-people-processes-and-technology-fe8473a1f34d">The Cost of Project Failure — People, Processes and Technology</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile Success Story: LEGO and their Agile Transformation]]></title>
            <link>https://medium.com/design-bootcamp/agile-success-story-lego-and-their-agile-transformation-2ac474d07ad7?source=rss-905e40c4bee9------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ac474d07ad7</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[Bosa Igbinoba]]></dc:creator>
            <pubDate>Wed, 10 Aug 2022 08:46:09 GMT</pubDate>
            <atom:updated>2022-08-10T08:46:09.005Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/650/1*HfQP7KmObVuysCZb4-TNxQ.jpeg" /></figure><p>Agile practices in software development encourage iterative and incremental development of high-quality working software that customers love. <a href="https://www.linkedin.com/pulse/big-companies-still-fail-agile-bosa-igbinoba/?trackingId=87YHHjVCRxS7gFqhD36W5Q%3D%3D">In last week’s piece</a> I suggested some big companies are still operating in a wasteful and antiquated manner when it comes to project management and digital solutions.</p><p>Today’s article focuses on LEGO and how one of the biggest and most loved companies in the world has embraced agile practices and have found success through their adoption of agile practices.</p><p>Before we proceed it’s worth noting that there is no silver bullet when it comes to software development, things can and will go wrong during a project, and to think that agile is a magic opiate or elixir that can exonerate all project/product development shortcomings is wrong.</p><p>Agile product development programs can fail for a plethora of reasons, but today we analyze LEGO, the fact they embraced agile and the successes that decision has brought to them.</p><h3>LEGO Digital Solutions</h3><p>The LEGO Group’s core philosophy is that high-quality play enriches the lives of children and enables creative learning.</p><p>Lego Digital Solutions (DS), is a branch of the Lego empire and they decided to transition to agile via the Scaled Agile Framework (SAFe) Agile framework in 2014. Since then, they have been operating with considerable agility.</p><p>Moreover, such a vision cannot be realized with one-off solutions, or myopic and lofty project goals and targets; instead, dynamism, high levels of responsiveness and full adjustment to constantly moving targets must be embraced.</p><p>To succeed, LEGO realized their employees had to innovate, test, and learn in a world that is in constant flux.</p><h3>Background to Scaled Agile Transformation</h3><p>According to Henrik Kniberg and Thyrsted Brandsgård, the agile coaches who led the agile transformation for LEGO DS the following problems were established:</p><p>Cross-team alignment: how to get teams moving in the same direction instead of stumbling over each other</p><p>Client collaboration: how to set realistic expectations and satisfy the clients without over-committing</p><p>Release planning: how to plan and prioritize work across multiple sprints, multiple teams, and multiple products</p><p>Platform development: how to make sure we invest for the future and don’t just implement a bunch of one-off solutions</p><p>As is the case in many pre-agile environments there was considerable confusion, inefficiencies, and lack of customer collaboration, all recipes for an ineffective and wasteful work environment.</p><h3>The Much-Needed Change</h3><p>The LEGO DS team consisted of 20 teams, so there was significant change and realignment required. According to Kniberg:</p><blockquote>We morphed the entire DS organization into a team-of-teams, introduced a shared sprint cadence, decentralized syncronization and dependency management, and big-room planning events every 8 weeks. This has had a whole lot of positive effects, not only for DS, but also for other departments that we collaborate with.</blockquote><p>The fourth agile principal reads:</p><blockquote><em>“Business people and developers must work together daily and throughout the project.”</em></blockquote><p>The culture morphed from a segmented and siloed environment to a collaborative one because of embracing and incorporating <a href="https://agilemanifesto.org/principles.html">Agile Principals four, five, six, eight, eleven and twelve respectively.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QgmkibYQjQttyv2F" /></figure><h3>The Results</h3><p>Agile practices are nuanced, so a distinct a-to-b relationship can be difficult to establish when measuring success. Is success financial? Cultural? Is staff retention, morale and productivity a factor? There are many methods and ideas that contribute to “success,” but in this case success looks like:</p><p>- Company and departmental adoption of agile</p><p>- Company culture of agile before and after</p><p>- Managerial benefits of agile adoption</p><p>As a result:</p><p>- Agile adoption transformed the organizational structure to a product-oriented team</p><p>- Local managers transferred ownership of deliverables to teams, thus empowering teams to be self-reliant</p><p>- Performance measures for bonuses were immediately changed. Individual targets were broadly replaced by team focused KPIs. Traditional, process focused KPIs were exchanged more gradually for value, product, and team measures.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nKVF6jE0zzdO3VNL" /></figure><p>As you can see from the graph above, agile implementation on a company level can be a slow, methodological process. Also, some departments like department C have fully or partially embraced, whilst B are a little slower.</p><p>Of the 40 departments surveyed 26 have fully or partially embraced agile practices, meaning 65% of the teams surveyed trust agile enough to make the digital transformation.</p><p>The table below summarizes the before and after of LEGO’s agile transformation:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DW9Vb-J8aGnfHfED" /></figure><p>Organizational change accompanied by operational resilience meant that agile practices could be fully embraced and adopted. <a href="https://www.linkedin.com/pulse/big-companies-still-fail-agile-bosa-igbinoba/?trackingId=sjJihLvVTJCFEPXDKNrvVQ%3D%3D">As mentioned in the last article,</a> there is a corporate rigidity in many large companies who don’t embrace agile practices and in LEGO’s case, SAFe’s scaled agile approach. Kniberg went onto say:</p><blockquote>“[Agile] has improved the motivation of the team members. Going to work is more fun when there’s less confusion and less waste. And motivated people do better work, so it’s a positive cycle! Another impact we’ve seen is that other parts of LEGO visit the meeting, get super inspired, and start exploring how to implement some of these principles and practices in their own department. In fact, agile is spreading like a virus within the company, and the highly visible nature of the PI planning event is like a catalyst.”</blockquote><h3>Case Study: Pop-Up Store</h3><p>LEGO sales teams wanted to find a way to boost physical stores dwindling sales and financial struggles. The team decided to create a series of pop-up shops to engage with customers.</p><p>This idea required a fast response from digital teams to create customer-focused and customer relevant inventory. The improved ability to respond, due to mass agile adoption allowed the digital teams to support the sales teams and create a positive shopper experience, whilst growing sales in the process.</p><h3>Case Study: Finance Product</h3><p>LEGO’s finance department requested a specific product to solve their internal problems. A traditional (waterfall) estimate suggested 8,000 hours of development time would be required to complete the project. The substantial (initial) estimate combined with a centralized managerial style meant the project was never sanctioned.</p><p>Agile transformation shifted prioritization to the finance team’s product owner and the product became the top priority. Because of this, an MVP was achieved in just two sprints! The sprints were two weeks long and the work was done in less than 800 hours, a tenth of the 8,000 hours estimated prior.</p><p>These savings and efficiency gains are rife within many large companies who make a proper transition to agile practices. What this example highlights are the potential pitfalls of hyperbolic and extensive planning at the start of a project.</p><p>The MVP didn’t have all the bells and whistles the original plan scoped for admittedly, but in just one month there was working software; a clear win for agile practices against more traditional methods such a waterfall.</p><h3>Case Study: Supply Chain</h3><p>Agile practices moved away from LEGO’s product development and digital transformation teams and moved towards their supply chain planning when LEGO management realized the responsiveness and malleability to an increasingly dynamic and evolving world was critical to success.</p><p>Unpredictability of market behavior has created a need for simpler, nimbler, and more intricate planning tools. Digital and business teams created a tool to meet the needs of both groups.</p><p>The teams didn’t spend substantial time building their supply chain solution, opting for a “good enough” tool instead. Functionality, based upon feedback and fluctuating market requirements were then iteratively added in increments.</p><p>This approach has empowered users who derive benefits months (if not years) prior to the initial go-live date originally estimated under the older, traditional system.</p><h3>Conclusion</h3><p>LEGO have demonstrated that proper agile adoption and senior stakeholder buy-in can transform product development and digital solutions on a global level. The pop-up store case study shows what happens when customer response levels are optimized and this can only happen if practices are suitable to change in real-time.</p><p>Overall, a company of LEGO’s stature and size are reaping the benefits of being small enough to be flexible in product development, but large enough to exploit scale; the winner here is agile!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ac474d07ad7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/agile-success-story-lego-and-their-agile-transformation-2ac474d07ad7">Agile Success Story: LEGO and their Agile Transformation</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sarina Wiegman shows us all what Effective Leadership Looks Like]]></title>
            <link>https://bosaigbinoba.medium.com/sarina-wiegman-shows-us-all-what-effective-leadership-looks-like-9a565a0c2522?source=rss-905e40c4bee9------2</link>
            <guid isPermaLink="false">https://medium.com/p/9a565a0c2522</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[success]]></category>
            <category><![CDATA[womens-soccer]]></category>
            <category><![CDATA[leadership-development]]></category>
            <dc:creator><![CDATA[Bosa Igbinoba]]></dc:creator>
            <pubDate>Wed, 10 Aug 2022 05:03:35 GMT</pubDate>
            <atom:updated>2022-08-10T05:03:35.911Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*g2yBHsLflaHZuSLecoCchw.jpeg" /><figcaption>© BBC Sport</figcaption></figure><p>The England Woman’s national football team have achieved a monumental feat in winning the European Championship for the first time in English football history.</p><p>As football is the national sport of England and the world’s most popular sport, we have witnessed, on a global level, what takes place when astute, effective, and cohesive leadership and teamwork synthesise to create and achieve monumental success.</p><p>Clearly, the beautiful game can teach us how to achieve project success, build and sustain winning teams, how to lead effectively and steer a team towards tangible success.</p><h3>Lessons we can Learn From Football</h3><p>At the heart of every great team is teamwork, team cohesion and more candidly, team chemistry. It is the willingness to cover your teammate, the genuine rapport built, the ability to get along with and the real and honest conversations you can have that lies at the heart of peak team performance and the Euro 2022 victory personifies great lessons we can all learn from.</p><p>Winning teams have high morale, genuine camaraderie, discipline and rigour and a true sense of togetherness and this stems directly from the leader/leadership.</p><p>England manager Sarina Wiegman was discussing the importance of using skill within build-up play and general attacking as a potential tactic and approach in an interview.</p><p>What was most interesting was before Wiegman even went into the football side of proceedings she suggested:</p><blockquote>“First of all, I try to connect with players, so you can connect, you start with a conversation, you learn about each other, then you have a football plan.”</blockquote><p>Immediately Wiegman shows glimpses of what kind of leader she is. Wiegman’s primary focus is on the person and ensuring there is an actual connection between her and her team before giving any football-related instruction.</p><p>A great leader is a people person first and last, without being able to bond with people you fail.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*INFvmnzwiWtSf0HR-Pn8XQ.jpeg" /><figcaption>© Getty Images</figcaption></figure><p>This might seem like a simple and logical first step but speaking from personal and professional experience, this step has unfortunately been overlooked many times, and has had detrimental consequences as a result.</p><h3>Wiegman’s Man-Management</h3><p>Lianne Sanderson, an English forward with 50 caps for England described Wiegman as the “missing piece” to English football. Sanderson, when asked by an interviewer about what makes Wiegman so successful and effective, Sanderson suggests:</p><blockquote>“From speaking to the players and from what I’ve heard I think it’s man-management and communication.”</blockquote><p>Rachel Daly, European cup winner goes onto add:</p><blockquote>“She [Sarina Wiegman] has brought directness [sic] calmness to the group. The way she views things is something we’ve never had before.”</blockquote><p>A great leader is decisive and an effective communicator, but directness and communication without approachability cannot work.</p><p>These complementary traits, amongst other winning traits such as positivity and trust have been exemplified best by England’s Women’s team and their amazing triumph.</p><p>It is said in football that a manager does their work on the training pitch and behind the scenes and the players do the work on the pitch, so the results and performance were the culmination of excellent leadership from Wiegman and high-quality teamwork from the England team.</p><h3>Seven Traits of Great Leadership</h3><p>Great leaders embody these characteristics in their personalities:</p><p>1. Positive Attitude</p><p>2. Proactive approach</p><p>3. Delegate and Trust</p><p>4. Approachable</p><p>5. Lead by example</p><p>6. Accountable</p><p>7. Decisive</p><p>These traits are a set, and a mix and match does not work. What Sarina Wiegman showed is that she has all these characteristics. Without any of them, the Lionesses would not have achieved such great success.</p><p>Wiegman was decisive by playing the exact same team from the first game to the last, not been influenced by the media and external stakeholders such as fans. Wiegman was clearly approachable due to many players praising her man managerial skills, her directness and honest communication.</p><p>These are just two that were on public display, but behind closed doors it is likely that the other characteristics were an active part of Wiegman’s leadership style.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qqcoa9CE8B0em9xRZRPYdQ.jpeg" /></figure><p>When a leader does show and demonstrates these essential traits a harmonious, robust, and high-morale environment is created.</p><p>Poor performance tends to reflect poor leadership more than it is of individual error or incompetence.</p><p><a href="https://www.linkedin.com/in/simonsinek/">Simon Sinek</a> wrote in his book The Infinite Game highlights why leaders must strive to create an environment for their team to thrive in:</p><blockquote>“Noah’s managers at the Four Seasons understand that their job is to set an environment for Noah in which he can naturally thrive. Leaders will work to create these environments when we train them how to prioritize people over results. And this is the true definition of what it means to lead.”</blockquote><p>This fits into last week’s article where <a href="https://www.linkedin.com/pulse/cost-project-failure-people-processes-technology-bosa-igbinoba/?trackingId=OrOkeGPSRtmPQq9lFraWhg%3D%3D">people, processes and technology</a> were discussed, and the people first mentality was shown to be the most important part of technology project success.</p><h3>Football Embodies Teamwork</h3><p>Typically, when the ball carrier has the ball his/her teammates attentively watch them whilst they progress with the ball. Off the ball, the closest teammate usually covers the space that has been vacated due to the progressive movement of the ball carrier and the whole team shifts across to maintain balance and shape.</p><p>For example, if Trent Alexander Arnold, right-sided full back for Liverpool FC is carrying the ball, typically, Jordan Henderson (who plays right-sided central midfield) covers the space vacated. This maintains team balance, shape, and structure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m_6h4dLcpCrpE1En1elkig.jpeg" /></figure><p>In the workplace, a good team knows that absence shouldn’t be severely felt because an effective leader ensures a teammate is covered. The leader produces an environment that radiates true rapport with themselves and with their teammates so that teammates are covered properly.</p><p>A good leader drills into his or her team the importance of covering for each other to maintain balance and shape. If the ball carrier loses the ball, then the space is not empty because a teammate has the space covered already.</p><p>Bad leaders create bottlenecks within their teams, whilst good leaders empower individuals to be confident and competent within a supportive environment where information flows fluidly and transparency is supported.</p><h3>Conclusion</h3><p>The European cup win shows the importance of high-quality leadership, a style that is easy to write about but not as common as you’d think. No matter the industry, high performing leaders put their people first.</p><p>The outcomes, complexities, intricacies, and the like will not miraculously fall into place, but without carefully cultivating and crafting an actual bond with a team, which will foster a healthy environment, results will be poor at best.</p><p>The worst leaders are hostile, rash, incompetent, erratic, shallow, insecure, and impulsive, failing to make any real connection with their team and alienating individuals without proper grounds.</p><p>These folk often result to tactics such as micro-managing, excessive and non-productive meetings, excessive and pointless paperwork and more time-wasting, non-productive and frankly useless methods to give the appearance of work, but no significant change in overall delivery or outcome.</p><p>Missed deadlines, over-promising and under-delivering, and unhappy stakeholders are just some of the hallmarks of poor leadership, irrespective of market, industry, or sector and this is rife in so many sectors today.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*8PAY4gm5SoYeUU6L0m1O1A.jpeg" /><figcaption>© Getty Images</figcaption></figure><p>Leadership starts and ends with effective people management. If you have a lot of knowledge, career credentials, experience, and so on, but you cannot convey that with empathy to your team, then those skills do not matter.</p><p>There is no successful outcome without successful teamwork and no successful teamwork without quality leadership; only when this is grasped will people in leadership positions, who aren’t necessarily leaders make the progress they seek.</p><p>A massive well done to the England Woman’s National Team for showing us all what excellent leadership and teamwork looks like!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9a565a0c2522" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Some Big Companies Still Fail With Agile]]></title>
            <link>https://medium.com/design-bootcamp/some-big-companies-still-fail-with-agile-f05a06b1e990?source=rss-905e40c4bee9------2</link>
            <guid isPermaLink="false">https://medium.com/p/f05a06b1e990</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Bosa Igbinoba]]></dc:creator>
            <pubDate>Tue, 09 Aug 2022 13:05:00 GMT</pubDate>
            <atom:updated>2023-09-05T23:31:11.021Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bwBE20qBBrw1L39b99vJVg.jpeg" /></figure><p>Knowledge is futile unless it is applied. Knowing things but not reaping the applied benefits can lead to frustration and waste.</p><p>Many leaders and senior staff in some of the world’s biggest companies are still developing digital solutions in ways that don’t exactly reflect efficiency, pragmatism, and optimal customer satisfaction.</p><p>Agile software development has permeated the vast world of software development for over 20 years now and shows little sign of slowing down. Not exclusive to IT, agile project management and product development has revolutionized the way in which digital solutions are implemented and maintained.</p><p>Despite the global popularity, a vast number of recognized professional accreditations, mass adoption from large and successful technology titans such as Amazon, Google, Apple and the like, many big companies not only struggle with agile practices, but actively operate using older methodologies such as waterfall. This article looks at the ramifications of such practices.</p><h3>Waterfall isn’t Optimal (Most of the Time)</h3><p>Development within waterfall cascades down, phases only start once the previous phase is completed. Tacitly this erects silos and barriers; walls that can become insurmountable in the long-run and prevent genuine transparency amongst the team.</p><p>Without transparency, proper inspection is limited if not non-existent, and without consistent inspection, adaptability is lost or heavily reduced. Transparency, inspection and adaptability are core pillars within the agile framework, these proven traits usually lead to better products in the long run.</p><p>Product Management authority Marty Cagan writes:</p><blockquote>“While we’re busy doing this process and wasting our time and money, the biggest loss of all usually turns out to be the opportunity cost of what the organization could have and should have been doing instead. We can’t get that time or money back. It’s no surprise that so many companies spend so much time and money and get so little in return.”</blockquote><p>The simple fact is resources are being depleted and end-users and are wondering where the time and money has gone. If you’ve been part of any project within a large organization, you’ll know this is unfortunately normal in so many cases.</p><p>Resources have been wasted and a huge reason is because of the way in which the project has been managed; waterfall projects in today’s world feels outdated and much less responsive to the needs of the customer.</p><p>This observation isn’t new, nor ground-breaking, but it’s amazing how many companies still operate in such an antiquated way, the question is why?</p><h3>Culture Clash</h3><p>An often-overlooked consideration for poor or no agile adoption stems from the fact that large corporations are simply not culturally known for being the most nimble, malleable, and pragmatic, especially when it comes to software solutions and digital transformations.</p><p>Large corporations tend to operate top-down, steering the ship all the way from the top and orders cascading downwards; everything going down, and very little going back up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*joSOoBMtAzY0IRoa8yp97A.jpeg" /></figure><p>To a large extent, every large company operates to some degree like this. Even the more receptive tech companies like Apple, Microsoft, Amazon, Netflix and so on all still maintain some degree of traditional corporate structure.</p><p>The key difference however is the fact that on the developmental/product innovation level, the level responsible for product design, software implementation and product management, agile practices are woven into all facets of their internal operations.</p><p>The results: constant innovation, market dominance and the ability to respond to customers in remarkable time.</p><p>Companies who truly adopt agile principles will drive recruitment that reflects this, teams will expect, maintain, and promote these traits and at most levels, agile principles are the norm.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R5_ksPoWCLDcCDHWhIQKGw.jpeg" /></figure><p>Furthermore, most of the innovation and “disruption” has come from companies who can respond to customer needs in a timely manner; only agile approaches can meet the customer needs in such a way.</p><p>Think of what Monzo has done to banking, Lemonade to insurance, Airbnb to hotels and hospitality and Twitter to public communication.</p><p>Do you really think these companies would have been able to disrupt the behemoth industries they have if they were not pragmatic, nimble and (of course) agile? No!</p><h3>Psychological Barriers</h3><p>Culturally, many (not all) large corporations have psychological difficulties in adapting to agile practices. Many senior staff ponder the notion along the lines of</p><p>“I’ve been doing this this way for most of my career, and it’s got me here, why should I change?”</p><p>Blockbuster and Kodak thought in the same way and those household names are now irrelevant and obsolete.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FVkGRgIDa1vPFuhzgwfkQQ.jpeg" /><figcaption>RIP Kodak and Blockbuster</figcaption></figure><p>The ability to respond to change and produce products that customers love is critical to survival in today’s product saturated world. Customers implicitly bring expectations and mannerisms from other apps when using similar apps.</p><p>This is done subconsciously, but it is a very real part of a user’s journey. When you look at Instagram’s latest interface for example, you can clearly see the fact that it is modelled on TikTok due to TikTok’s dominance in social media.</p><p>This is relevant because it demonstrates two significant points: firstly, Instagram understands what is described in the Laws of UX as Jakob’s Law, the idea that users expect your site, app, platform etc., to work and operate in the same way as others, in this case, the market leader, TikTok. A quote from Jon Yablonski’s Law of UX reads:</p><blockquote>“This observation, which Nielsen describes as a law of human nature, encourages designers to follow common design conventions, enabling users to focus more on the site’s content, message or product.”</blockquote><p>Without the Instagram staff being close to customers and understanding their needs, changes like this would be timely and costly to scope, implement and deploy.</p><p>In truth, we don’t know the specifics of their UX/UI update, but it does reflect agile in the sense that customer collaboration, inspection and adaptability and changing requirements is reflected in the product constantly.</p><h3>Product Management &gt; Project Management</h3><p>The responsiveness to change and customer satisfaction is perhaps the clearest distinction for the need for ample product management as opposed to traditional project management.</p><p>Projects follow timelines, milestones and tend to resist change, even if customers desire change.</p><p><a href="https://nashtechglobal.com/our-thinking/insights/large-organisation-agile-adoption/">According to an article from Nash Tech</a> agile adoption is slow for two main reasons: large companies desire for predictability and long-standing traditions.</p><blockquote>“Whether it’s about cost or outcomes, predictability is important to large organisations as small mishaps may lead to large regulatory or financial impacts. Big firms want to know upfront what they’re getting, which often means extensive requirements documentation.”</blockquote><p>According to a report from Capgemini:</p><blockquote><em>“Scaling agile leads to significant value upside, yet only a handful of organizations are successful at it.”</em></blockquote><p>Product management actively incorporates change in a fluid, responsive and elastic way due to the core principles and practices of agile being embedded into the tools, artefacts and mannerisms of what product management is.</p><p>Maybe this approach is deemed too risky for so many decision makers. Are agile principles only adopted by the risk adverse?</p><h3>RAG is the Measure of Progress Not Working Software</h3><p>Senior stakeholders at many companies tend to operate from a top-down, high-level perspective, expecting where and when key milestones will be delivered and accomplished.</p><p>There are cost pressures, investors, and other senior stakeholders who have a significant stake in the outcome of the project. Therefore, it makes sense to have a good idea of where and when key milestones will be delivered. Right?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uRfh_VzyhfFIZQBBwAYq8w.jpeg" /><figcaption>RAG — Red, Amber, Green — Photo by <a href="https://unsplash.com/@neotronimz?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Nirmal Rajendharkumar</a> on <a href="https://unsplash.com/s/photos/traffic-lights?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>One problem… We know the least at the beginning and this is when we are expected to have a good idea of how things will unfold!</p><p>A major problem with planning, especially at the start of the initiative is the lack of understanding and clarity of the road ahead.</p><p>This is because at the start you naturally know the least, therefore, the plan is not going to be the accurate due to the lack of information.</p><p>Now, pragmatism and the ability to be malleable or agile is welcome here, right?</p><p>Well, so many companies still believe in sticking to plans with ferocious rigidity. Plans become sacrosanct; they become project ‘idols’ that are the be-all-and-end-all of project progress. Project ‘success’ is marked by the ability to stick to the plan as best as possible, any deviation is seen as a failure.</p><p>So, additional meetings to ascertain why the RAG is amber or red now fills diaries, creating more time away from the desk and time is spent (or wasted) on calls/meetings to explain why the plan has been altered and when development will return to the original (outdated) plan trajectory.</p><p>It isn’t uncommon to not have any working software, vis-à-vis, software the end-user can actually use to solve a problem 6 months or 12 months after project kick-off!</p><h3>Plans are still relevant in Agile</h3><p>It is a good time to remind you that agile practices do not eliminate planning. Agile practices still view plans as important as they can help teams stay focused.</p><figure><img alt="Asian woman doing financial presentation in boardroom with multi ethnic group. Team of people looking at statistics and graphs on monitor to plan research project for business growth" src="https://cdn-images-1.medium.com/max/1024/1*t0AFMNEpmnBK7eDaly2S5Q.jpeg" /></figure><p>However, a plan that was derived 6 months prior, when information was scarce, the team knew least about each other and best practices, knew least about their internal workflows, processes, development time, the customer’s needs, their velocity and so on, should naturally change.</p><p>But many companies still don’t operate like this. In some cases, companies double-down and insist on even more plans.</p><h3>Conclusion</h3><p>In truth, an entire book could be written on this issue, but for now, it’s important to remember that some big companies are still wasteful when it comes to product development due to the fact they struggle to transition and truly adopt and embrace agile practices.</p><p>In the long run they will continue to lose money and time and struggle to hire the very best talent that is available as the best people tend to want to be part of innovative and rewarding work, not wasteful and stress-inducing work.</p><p>A combination of psychological, historical, traditional, and economic factors plays a part. Bottom line is, many of these companies are shooting themselves in the foot due to the opportunity cost of what they produce vs what could be, and this won’t last forever; eventually the penny will drop, but at what cost?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f05a06b1e990" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/some-big-companies-still-fail-with-agile-f05a06b1e990">Some Big Companies Still Fail With Agile</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>