<?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 Isidore Onyeako on Medium]]></title>
        <description><![CDATA[Stories by Isidore Onyeako on Medium]]></description>
        <link>https://medium.com/@isidoreony?source=rss-3df3c6b5298c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*C0m4AmjqBKB_JRo8.jpg</url>
            <title>Stories by Isidore Onyeako on Medium</title>
            <link>https://medium.com/@isidoreony?source=rss-3df3c6b5298c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 17:54:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@isidoreony/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[Traceability and Quality Engineering]]></title>
            <link>https://isidoreony.medium.com/traceability-and-quality-engineering-10f42c94ff9a?source=rss-3df3c6b5298c------2</link>
            <guid isPermaLink="false">https://medium.com/p/10f42c94ff9a</guid>
            <category><![CDATA[pdca]]></category>
            <category><![CDATA[iso-9001]]></category>
            <category><![CDATA[traceability]]></category>
            <category><![CDATA[quality-engineering]]></category>
            <dc:creator><![CDATA[Isidore Onyeako]]></dc:creator>
            <pubDate>Sat, 27 Mar 2021 15:45:26 GMT</pubDate>
            <atom:updated>2021-03-27T16:34:21.641Z</atom:updated>
            <content:encoded><![CDATA[<p>Today, I decided to extend my knowledge of Quality Engineering and ISO9001:2015 to engineers and career minded people following me here. I will try to keep it less technical. ISO9001 uses process approach to manage quality. In reading this post, I will like you to map or relate the knowledge you get here, to the things you see around you both in the news and the physical world. For instance, think of how Nigeria would have been if this mindset is applied to how it is run and systems operating in Nigeria.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/548/1*Rf8dN4SsaZDRwrATyqTuSw.png" /></figure><p>ISO9001:2015 PDCA (PLAN-DO-CHECK-ACT)</p><p>With Plan Do Check Act (ISO PDCA), it is easy to appreciate the power of a process approach to modeling solutions and solving problems generally. Process approach means you receive an input, you do work with or on the input, then you produce an output. The PDCA says, you say what you will do; you do what you said you would do. That means there should be a means to check that what you did is what you said you would do. Then there should be another process to correct situations where you did not achieve what you planned to do or you created new problems. Then the cycle continues and you keep getting improvements as you go.</p><p>You can see there is an expectation of a system to document these processes. There should be a system to document the planning process. There should be a system to document or support the “doing” process. There should also be a system for controlling the “checking” process as well as a system to support the “acting” process.</p><p>The above represents the core sources of solutions and systems you see all over the world today. So, it also means that, without sounding like a motivational speaker, if you understand this, you should be running big organizations and creating value by solving problems.</p><p>TRACK AND TRACE</p><p>This post is not about about ISO9001 and PDCA. I used it to lay a foundation for the analysis of Traceability in Quality Engineering. 5 years ago, Volkswagen was fined $2bn for lying on emission results. it was gathered that they tricked their cars to out emission measurements to lie the machines that report the emission results. With this, they went to market and sold their cars as low emission vehicles and made a lot of money. When this was discovered, they were fined and their CEO resigned. There was also a global apology tour which no one cared about really. People liked their cars anyways. 10 years ago, Toyota cars were recalled for having faulty airbags and also another incidence was traced to faulty brake systems. The faulty airbag was of great interest because it involved one of their vendors (Takada). Takada made airbags for almost all auto makers. This means that through the Toyota incidence, Takada was able to claim it affected nearly all car makers. When Volkswagen emission issue came up, their cars were also recalled. This recall process is what this post is about.</p><p>TRACEABILITY DEFINED</p><p>Keyence defined traceability as the ability to trace all processes from procurement of raw materials to production, consumption and disposal to clarify “when and where the product was produced by whom.” With the ISO9001 mindset, we start traceability from planning for quality. We document all the plan for making a product. Then we trace all the equipment used in making the item; who worked on what and which materials were used in making what and at what time and what was the outcome of such actions. This is where data collection systems play a huge role. Meanwhile, it is imperative to note that data collection is not enough in traceability. There needs to be an association between the quality plan and the execution actions. An example is that merely saying that we checked that you placed part B on part A using equipment C on Tuesday and that the outcome was a PASS after verification, is not enough. We need to trace that the action you did is defined in a plan and that your work referenced that plan.</p><p>The use of serialization is extremely critical in traceability. Even in Lot or batch production, it is important to target small lots. In fact, the objective function in traceability for batch production is to minimize batch sizes. If more than one person is working on a process in a batch at once, you cannot trace any item on that batch to any individual person. If this is the intention, the batch must be reduced to such size that one person can finish the work on one batch without affecting the throughput of the system.</p><p>GENEALOGY and FAMILY TREE (PARENT-CHILD)</p><p>When items are built or assembled, it is imperative that we document all the components that are in the assembly. Dell was the first to pioneer this solution in their ordering process and it made them the leader in online sales of laptops and computers. When you placed an order those days on Dell website, a packing slip will be produced and the serial number of parts to be assembled in your computer or laptop will be added in the packing slip accompanying the digital invoice Dell would send to you. And when the item is shipped, you would see that these were the exact serial numbers on the product.</p><p>The details of traceability is outside the scope of this post, we are interested in the value of traceability. When it was determined that an airbag used by Toyota was faulty, a genealogy report was generated. This report would be generated to know the vehicle ID or a top level assemble reference of the applicable part. With this reference, a report can show all the end users of the cars into which the parts were assembled. In a nutshell, the parts that were faulty (break system), were manufactured as part of a batch or lot. The batch or lot is the anchor for tracing all the instances of this part made in that lot or batch. For each item in that lot, a reverse recursive (bottom to top) genealogy report will be used to determine the vehicle ID’s (VINs) of cars into which the breaks from the faulty lots were assembled. Then the maker (Toyota) can issue a recall notice to all owners of the vehicles.</p><p>The above now means that the fact that Toyota has this traceability system has significantly minimized the risk of the failures of the parts (break system) in the field. Consider that Risk valuation is a function of probability of occurrence and impact. Even when the impact is high (people dying), if the probability of occurrence is zero by way of replacing the parts even before the accident happens, the risk has become 0.</p><p>This knowledge and mindset apply critically in pharmaceuticals, automotive, medical, military, and aerospace industries. What is most important is that you don’t fix an issue and wait for the next occurrence of the issue to happen. You notify users of your product or send parts out in the field for the issues to be corrected an further prevent the negative occurrence (risk) from happening.</p><p>I conclusion, it is important to note that there is no limit to the number of systems that can be built and value created if we are interested in solving problems</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10f42c94ff9a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On Startups, Business Partnerships & Sustainability in Hitech]]></title>
            <link>https://isidoreony.medium.com/on-startups-business-partnerships-sustainability-in-hitech-510cdb60e604?source=rss-3df3c6b5298c------2</link>
            <guid isPermaLink="false">https://medium.com/p/510cdb60e604</guid>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[nigeria-tech]]></category>
            <category><![CDATA[forecourt-automation]]></category>
            <category><![CDATA[payments-technology]]></category>
            <category><![CDATA[storefront]]></category>
            <dc:creator><![CDATA[Isidore Onyeako]]></dc:creator>
            <pubDate>Sun, 14 Mar 2021 23:15:20 GMT</pubDate>
            <atom:updated>2021-03-14T23:15:20.187Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/978/1*fjsl5sr97w_-A8_MRPVKiA.png" /></figure><p>Four years ago, I decided to create a startup to solve a critical problem in the oil and gas sector. We all know that there is so much gaps in this sector ranging from lack of fidelity and accountability to general inefficiency and the scourge of excessive cash on the streets that should actually be in the banks. We all know the industry is in dire need of innovation. Wikipedia described a startup as a company or project undertaken by an entrepreneur to seek, develop, and validate a scalable economic model. Note that the goal is to validate a scalable economic model. This means that at the initial stage, the focus of the startup is never to run the business but to use skills and flexibility to tackle the particular problem.</p><p>It is imperative to note that anybody can form a startup. Mainstream organizations can form a startup. What is key here is that the mainstream organizations have rigid structures, governance procedures and potential knowledge silos that would make it difficult or almost impossible for them to tackle the problems. For mainstream organizations to solve these problems, they have to setup what is called skunk works or small team of dedicated and skilled resources that will work in a very flexible manner to deliver the solution. The above model is very common n Silicon Valley and North America where I actually work.</p><p>Another way a mainstream organization can get close to solving this problem is by partnering with a smaller organization to form the startup. In this case, the smaller organization will be the startup while the mainstream organization is the backer. The backer provides all the necessary activators like funding for equipment and research. All the startup needs is to continue to churn out intellectual property (IP). Products are built on intellectual property. IP can be an idea or even a way a problem is solved. In any case, it has to be effective and unique.</p><p>I founded my company after I was visited by some investors from Southern Oregon. They wanted me to build the solution for use in America. We decided on the company name in my house and my wife approved it. That one is approver in chief. Whatever she approves pretty much has a high guarantee of success because she sees things a little differently when she gets the time to pay attention. When I started building the solution, I determined that America may not be the best market for now. I decided to face Nigeria. This started my journey back to Nigeria for this work.</p><p>I visited the biggest fintech in Nigeria with my equipment. They watched me open my bag, bring out all the wire, took 15 minutes to connect all of them and told them I am ready. Then I pressed the start button and the lights came on and in seconds, I was controlling a simulator pump with an app and the show went well. After that, they asked me if I built the system, I said yes but with my partner (who is the overall best student in FUTO during our time) and that my partner bought his home near mine in Canada for the purpose of building this solution and more. I told them I am the system engineer in charge of product and business, while my partner is the software engineer in charge of process and framework. I also write codes and actually design the product (software and hardware) and occasionally consult my partner to ensure we are using best practice. My partner told me that they want to invest in my company. I told them I came there to ask them to be my partner because I knew I would not be able to carry the business when it scales.</p><p>My partner told me that over 20 companies came to them to use them as the gateway and payment which is a different form of partnership. But that they also plan to be a player in this technology space. I told them I am OK with that and in fact, that after this one, I will start building another solution.</p><p>My partner invested in the company via equipment purchase worth millions of dollars. We agreed they will be the payment partner as well as business carrier. This relationship has been going well. Now, we have developed over 8 core IP’s that are now being planned for scale nationwide.</p><p>The summary of the above relationship is that we made sure it is about strength not just business. For instance, our partner is the best at payment switching and they are well established in Nigeria. In any case, their size and operational setup presents a significant drag to our progress but beyond all that, I often remind myself that if you want to go fast, you go alone but if you want to go far, you go with people. There has been hiccups and I was always on hand to resolve them. This led to my visiting Nigeria 10 times in 2 years and bringing Europeans to work in the field of Lagos with me. Today, we have a solution that actually works and sales people have started work.</p><p>It is also worthy to note that for my own startup, I made sure I offered my research and development partner a significant interest in the startup, to keep him. This is also another mistake people make. You give somebody writing your code and platform 5% of your company. Then in the middle of project, he finds a better offer or another job and ignores your project. My Canadian partner’s share is close to mine. Whenever we get into fights, I remind him that he is a cofounder and co-owner of the company and that I have no interest in investing in motivating him to work. This makes him feel embarrassed because no one wants his company to suffer. To that effect, he has been more hardworking than myself in the company. Other key stakeholders were vendors in Europe, China and North America. When we work together, we ask them for components of their solutions not the entire solutions. When they see how we work, they agree because they see us as a threat to their spread in Nigeria. The only option they have is to give us what we need as a disincentive to pursue research in their own area/technology.</p><p>I was called in to develop a model for RMS (Remote Management Systems) for cell towers in Nigeria. My model is always to build the solutions with American and European standards but at a cost affordable to African companies. I built the core system that costs $400 for $100. This meant that I could start the conversation. We stalled in the development of key partnerships. The reason was that we needed subject matter expertise. This is the person that knows about the industry and their requirements. In other areas of the partnership like R&amp;D, technical support, operations and business development, we already had coverage with our other key partners.</p><p>This is where this post starts to make a case that our people did not get a good training in universities about business. The prime who brought us in is also a FUTO graduate Austin). Austin worked in the biggest telecom in Nigeria for 20 years (according to him). He jokingly asked me earlier how I was able to secure the partnership with the fintech. I told him it was the fintech that managed to secure the partnership with me because they are the ones who take this more seriously. For us, we are merely interested in proof of concept (POC) and proof of value (POV). I did not pay close attention to that question then until we started our engagement with Austin.</p><p>Austin took me to a big player in VGC. I was meant to pay for the dinner (N57,000). I did not care that much because I wanted to get to the root of it just out of curiosity. When we got there, I observed he and the CEO wanted me to agree to give Austin the operations piece of the pie. We chatted back and forth about Nigeria and its regular challenges. I was just relaxing with them until it was brought up on 3 occasions that if Austin is not given the operations that the deal was off. I then switched to business mode and asked them what the deal actually was. I told them that the business has to be funded. I told them the fact that I said the funding is not an issue does not mean the money would fall from the sky. We needed to know if there is a business opportunity first. Also, I told them that when I see significant business opportunity to actually get my interest, that I will think about who will be the best to support operations. I know Austin will not raise enough capital to support the technology nationwide. Therefore, whoever will support the technology will want to be given a share of the business. However, I told them that one thing I know the enterprise will need and which only Austin can do is subject matter expertise. Now, this means that if we have a business, Austin will do nothing but just be the one to say we got things right and when any client or industry person raises concern about our technology, Austin will be the one to explain how our systems meets or exceeds the requirement because he is the expert that defined and approved it. For this even, we are ready to give him a significant share of the business.</p><p>The above is important to review because it happens to be where I drew the line. There is supposed to be over 20,000 cell towers in Nigeria with a potential for us to support. Austin wants to be the one to be going there to install, and check when there is an issue, fix it etc. Meanwhile, I have a partner who has over 5000 vehicles and personnel in Nigeria, who will handle this effectively under Austin’s guidance. As a business man, I will not be bullied into lowering the outlook of my enterprise because I want to be a nice guy. This is business. Therefore, that engagement is stalled.</p><p>To prove that subject matter expert is important, we started another major enterprise to solve a problem for market traders. Traders want a way to sell their products fast. Today, customers are having to drive to the various markets to get their products. We also know that the eCommerce ecosystem is showing promise but they seldom get anywhere close to the effectiveness of the guys in the various markets. We have the capability to build any system. We can build any ecommerce platform but we will be stupid to build the platform and then realize we just ended up with a generic solution like the ones we see in Jumia and Konga. We have also seen a lot of uptake for startups like Paystack (who raised $200million), OPay (Who raised $200million), Flutterwave (Who raised $170 million last week) and Interswitch (who also raised $200million last 2 years). We know that whatever we will do must not be what these guys are doing. We have to look for new problems in the market to solve. For this, we partnered with Obie Muoma.</p><p>Obie is a market player and we have validated his capacity to understand the market, the mindset of the players as well as their key pressure points. We have built the platform to address all the needs he identified. In April, the solution will be thrown to the market and we see how things go.</p><p>If it has not been made clear enough so far, the main purpose of this post is to make a case for the following</p><p>1. We need startups in Nigeria</p><p>2. Private sector has a role to play in tackling our problems in Nigeria</p><p>3. Big organizations are not well suited to solve these problems from a capability standpoint due to rigid structures and vertical silos</p><p>4. Big organizations are needed to solve these problems from a capacity standpoint</p><p>5. Subject matter expertise is critical and in very short supply in Nigeria</p><p>6. Partnership is important but delineation of domains is critical. Do not take up a task your partner is obviously better at</p><p>7. Think more about problem solving than business. Every problem effectively solved is a business waiting to be explored</p><p>8. Ensure all stakeholders validate their interest before signing documents.</p><p>9. A startup should be ready to sell to a more funded and equipped carrier.</p><p>10. You can be a serial entrepreneur like Elon Musk, Jeff Bezos and Tesla if your focus is problem solving. Musk and Bezos are not broke guys.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=510cdb60e604" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>