Category Archives: Technology

Risky Business: Part 2

No Gravatar

Yesterday (Part 1), we discussed why we need risk assessment- and alluded to why we fail this process.  We really do not understand risk, at all. The chance that a nuclear reactor will experience catastrophic failure in any given year is pretty low; but the probability of a nuclear accident happening anywhere is much higher.  The same is true when one considers a terrorist attack or even possibility of another BP oil spill.  And, the wild card in every calculation is human error (or stupidity).

Continue reading Risky Business: Part 2

Share this:
Share this page via Email Share this page via Stumble Upon Share this page via Digg this Share this page via Facebook Share this page via Twitter
Share

Our success may be due to luck- so we learn way more from failures.

No Gravatar

For the past 60 days or so, one of the prime topics of conversation has been the BP oil spill. This situation (fiasco? debacle?) is a great way to being discussion about our perceptions of risk (poor, at best). But, I will leave that concept for another day. Instead, I will discuss our ability to analyze our abilities to determine success.
Prior to 20 April, we thought we have solved the problem of deep-water drilling. After all, we were recovering billions of barrels of oil from the Gulf of Mexico for a long time. Had we written our history books on the 19th of April, they would all laud our ability to solve these problems.
Likewise, until 2009, Toyota was considered a technological marvel, a paragon of attention to customer needs. Books HAVE been written about its success. Alas and alack, they were a day early and way off the mark. (Actually, in Toyota’s case, they were not off the mark for most of the period. Instead, Toyota changed its business rules and concepts- to the detriment of its brand.)
This is exactly how we analyze most things. Those of us who start companies (or are hired to run them) all take great comfort in how well things run (generally). And, when they run well, we crow about how well we managed to design our business models. Unfortunately, many of these businesses are more lucky than well run. Moreover, because it is not clear how much luck played a part in the venture’s success, it is hard to assess “lessons learned”.
No, we learn far more from our failures than our successes. I admit, some of our failures could be due to luck. But, because we failed, we analyzed. We determined (assuming we were totally honest) what role everything played in our demise. And, then, we developed new systems to insure that a repeat performance was not among our future repertoire.
We may not all be guilty like BP/TransOcean/Halliburton. (I list all three because each one contributed to the disaster; the ultimate culpability will be determined later). To be honest, the biggest problem was overconfidence. We had been doing it forever; we were really smart and could start looking for ways to make more money by cutting corners. Oops- not true.
This is exactly what Toyota did. It’s what our mortgage bankers did. And, it’s what we could do just as easily. We need to take the time to analyze all potential failures- each time we change a process- business or production or technical.
As another example, many years ago, we hired an individual who was talented- and overqualified- for the position advertised (and for which he was ultimately hired). But, he was desperate for work (we were a technical firm in a small town; entities such as ours were not prevalent in the area, and he loved the area). So, we hired him.
As his experience with us (and ours with him) developed, we gave him more leeway and authority. He was working on our team to develop a new method to pasteurize (sans heat) apple cider. Our bench testing and our pilot plants all showed that our design was on the mark. We gave this individual the chance to scale up the process and oversee its installation at the actual facility.
It wasn’t a big project (as our projects went), but the next phase was worth about two to three times his salary. He was thrilled. And, he made a mistake- one that cost us about four times his salary to fix (and to vex us until we completed the redesign/reinstall).
He- and several of us- effected a complete post-mortem, after the client was satisfied. We determined where the errors were made, why the choice was incorrect, and what we could learn from this for all of our designs.
The key point is that individual managed to become the COO  of one of our operating companies. He knew the costs of failure, learned to examine “obvious” facts that are often wrong, and how to anticipate and correct deviations.
That never would have happened if his project management had proceeded without a hitch. And, from that error, we learned much and he learned much, so much so that he helped us generate more than 50 times his salary for the next decade.

Continue reading Our success may be due to luck- so we learn way more from failures.

Share this:
Share this page via Email Share this page via Stumble Upon Share this page via Digg this Share this page via Facebook Share this page via Twitter
Share

Our success may be due to luck- so we learn way more from failures.

No Gravatar

For the past 60 days or so, one of the prime topics of conversation has been the BP oil spill. This situation (fiasco? debacle?) is a great way to being discussion about our perceptions of risk (poor, at best). But, I will leave that concept for another day. Instead, I will discuss our ability to analyze our abilities to determine success.
Prior to 20 April, we thought we have solved the problem of deep-water drilling. After all, we were recovering billions of barrels of oil from the Gulf of Mexico for a long time. Had we written our history books on the 19th of April, they would all laud our ability to solve these problems.
Likewise, until 2009, Toyota was considered a technological marvel, a paragon of attention to customer needs. Books HAVE been written about its success. Alas and alack, they were a day early and way off the mark. (Actually, in Toyota’s case, they were not off the mark for most of the period. Instead, Toyota changed its business rules and concepts- to the detriment of its brand.)
This is exactly how we analyze most things. Those of us who start companies (or are hired to run them) all take great comfort in how well things run (generally). And, when they run well, we crow about how well we managed to design our business models. Unfortunately, many of these businesses are more lucky than well run. Moreover, because it is not clear how much luck played a part in the venture’s success, it is hard to assess “lessons learned”.
No, we learn far more from our failures than our successes. I admit, some of our failures could be due to luck. But, because we failed, we analyzed. We determined (assuming we were totally honest) what role everything played in our demise. And, then, we developed new systems to insure that a repeat performance was not among our future repertoire.
We may not all be guilty like BP/TransOcean/Halliburton. (I list all three because each one contributed to the disaster; the ultimate culpability will be determined later). To be honest, the biggest problem was overconfidence. We had been doing it forever; we were really smart and could start looking for ways to make more money by cutting corners. Oops- not true.
This is exactly what Toyota did. It’s what our mortgage bankers did. And, it’s what we could do just as easily. We need to take the time to analyze all potential failures- each time we change a process – business or production or technical.
As another example, many years ago, we hired an individual who was talented- and overqualified- for the position advertised (and for which he was ultimately hired). But, he was desperate for work (we were a technical firm in a small town; entities such as ours were not prevalent in the area, and he loved the area). So, we hired him.
As his experience with us (and ours with him) developed, we gave him more leeway and authority. He was working on our team to develop a new method to pasteurize (sans heat) apple cider. Our bench testing and our pilot plants all showed that our design was on the mark. We gave this individual the chance to scale up the process and oversee its installation at the actual facility.
It wasn’t a big project (as our projects went), but the next phase was worth about two to three times his salary. He was thrilled. And, he made a mistake- one that cost us about four times his salary to fix (and to vex us until we completed the redesign/reinstall).
He- and several of us- effected a complete post-mortem, after the client was satisfied. We determined where the errors were made, why the choice was incorrect, and what we could learn from this for all of our designs.
The key point is that individual managed to become the COO  of one of our operating companies. He knew the costs of failure, learned to examine “obvious” facts that are often wrong, and how to anticipate and correct deviations.
That never would have happened if his project management had proceeded without a hitch. And, from that error, we learned much and he learned much, so much so that he helped us generate more than 50 times his salary for the next decade.

Continue reading Our success may be due to luck- so we learn way more from failures.

Share this:
Share this page via Email Share this page via Stumble Upon Share this page via Digg this Share this page via Facebook Share this page via Twitter
Share

First they ignore you, then they laugh at you, then they fight you, then you win…

No Gravatar

I heard this quote (Mohandas Ghandi) earlier this week and it reminded me that this was how many of the new products/ventures with which we have been involved progressed. It is something to take to heart- and use as you grow your venture or introduce a new product.
I will provide an example, with certain information omitted. A few years ago (ok, let’s not get TOO accurate) we developed this household consumer product . It was a pretty novel idea (if I say so myself). But, no one really paid attention to the venture OR the product. After we got a little publicity, a few consumer firms actually called to say that we were crazy. I admit, we were (are?) a cocky bunch, so it did not faze us much, but it was hard to take as it kept coming, even from some of the large chains where we were hoping to have the product shelved and sold.
By the end of the first year, the product (we were managing this for our client) was generating about the sales volume we had projected (we were a month behind in our projections. And, all of a sudden- we found that one of the companies that told us we were nuts- was coming out with a competing product.
The good news is that ours was better. Our tests showed that our product (a cleaning item) provided about a 10% increase in whiteness, compared to theirs. We used that as part of our campaign. We even made an improvement in the packaging (which increased the shelf life of the product), which helped us out. But, our competitor actually matched this change. (Our product was not patented; it was very hard to reverse engineer.)
By then end of the second year (when our involvement was scheduled to terminate), our client had 80% of the market share- and exceeded its goals for sales, as well.
The lesson is you should use the time when the marketplace ignores you to insure that all your ducks are in a row, the testing matches your goals, and you are developing your organization. You will need this to bolster your egos when you are being derided. But, this lead time (especially if you are small entity) gives the time to fine-tune your business processes for the coming battle, when you do have competitors. And, as you refine and calibrate your processes for the changes in the market place, you can insure your ultimate win.

Share this:
Share this page via Email Share this page via Stumble Upon Share this page via Digg this Share this page via Facebook Share this page via Twitter
Share

Cement- a major source of carbon dioxide emissions and water usage- redefined

No Gravatar

Many of you know that MIT is one of my almae matres. I chose it both due to a personal reason (my ex-wife was accepted to BU) and because it was the antithesis of my undergraduate haunts. Brooklyn Poly basically taught one how to make things work (and minimized the theory). MIT was “gung-ho” on the theoretical aspects and less interested in real-life situations. I melded both of those attitudes into a balanced approach to engineering/business issues. Well, I just attended an MIT event that – at least for these disciplines- demonstrated that MIT is now interested in both.
MIT Professor Franz Ulm described his work with concrete. This is the most widely used man-made material in the world. Cement is among the oldest engineered construction materials, dating back to the Roman Empire (remember seeing all those extant aqueducts?). It basically starts out as limestone and clay mixtures that are then crushed into powder, and then subsequently heated to a very high temperature (1500 C) in kilns. This forces transformation of the materials, with tremendous potential energy bound into the powder. Upon mixing with water, the energy employed to bond the units into calcium-silicate-hydrate (C-S-H) complexes. . (Cement is NOT a molecule; while one could consider the composition to be (CaO)1.65(SiOs)(H2O)1.75, this is an approximation. ) At the microscopic level, these CSH units serve as a binder for the added sand and gravel ; this mixture is the concrete. Most of the carbon dioxide emissions in this manufacturing process result from heating the kiln to a temperature high enough to transfer energy into the powder. (Limestone is CaCO3; the heating removes the CO2 and the calcium oxide (CaO) is the active unit in the precursor)
There are some 25000 million tons of cement produced annually; all metals only account for 1350 million tons. More importantly in light of our desire to lessen our carbon footprint, this represents 32.5 billion GJ (gigaJoules) of energy, compared to 26.5 for metals. (And, notice how much MORE energy is required for the production of those metals.) This is equivalent to the power produced by some 700 nuclear power plants. There is one (1) cubic yard of concrete for each person on earth and 5% (some say 10%) of the earth’s CO2 emissions results from concrete manufacture.
Another way of looking at this is that 8 tons of concrete or 1 ton of cement is equivalent to 1 ton of carbon dioxide. If we could cut the carbon dioxide use by altering our cement technology, we could go a long way to solving our carbon crisis. This is even more critical when one recognizes that we are currently using some 3200 million tons of timber, while the earth is creating 2500 million tons a year.
If we converted all our heating to clean energy and sequestered carbon dioxide (solar, wind, etc.), our carbon dioxide emissions in 2050 will be on par with those of 2005- not much change. If we improved our concrete production technology, we would REDUCE our impact by 83% compared to 2005. It was estimated that if Europe (or America) would impose a carbon tax of $ 40/ton, it would wipe out concrete production in those areas, since it would be cheaper to import the concrete from Egypt.
By improving the strength of our concrete, we could reduce the size of our concrete beams and columns. There is an inverse relationship between size and strength for columns and perfect shells; the relationship for beams is X to the -2/3 power [ed:  NO superscripts seem to work here] . If we double the strength, we halve our carbon dioxide usage.
The process that he discussed involves ordering the atoms. (Remember, cement is NOT a molecule- see above) ; while one could consider the composition to be (CaO)1.65(SiOs)(H2O)1.75, this is an approximation. ) Normal concrete has a random structure; if we order it to make it more closely compacted (from 64% of volume to 74%), the strength is radically improved. [Although this was not discussed, these numbers closely match how crystals exist in nature. The most common structure is body centered cubic, which has a packing factor of about 68%; face centered is 74% packed.]
Even with all of these factors, the best approach is not for universal changes in concrete production, since there is a higher need for quality control and more skilled workers. The best approach for this use is in precast concrete used for bridges and special buildings. One example he cited was the Jakway Park Bridge In Iowa. This bridge used precast concrete 7.5 cm thick- instead of the normal 20 cm or so thick beams.
In addition to ordering the atoms to be more closely packed, the discussion included the incorporation of fibers and nanoparticles of titanium dioxide. The former usage increases the durability dramatically; the latter provide an added environmental benefit. When you incorporate the TiO2 nanoparticles, the ultraviolet irradiation in sunlight activates the oxygen atoms at the surface to break down NOx molecules; reducing air pollution. (This technology is in use at the Jubilee Church, formally known as Dio Padre Misericordioso. In addition to the air pollution benefit, the TiO2 keeps the concrete white (aesthetically pleasing; titanium dioxide is how we get “white” paper) and the concrete maintains the temperatures more evenly.)
What was NOT discussed was the water needs for this new concrete. When I inquired, Dr. Ulm pronounced that this would reduce the water usage concomitantly. It should be noted that concrete is one of the largest consumers of water in industry; it is why most concrete facilities are near water sources and why water reuse projects have focused on just that industry segment, as well.

Share this:
Share this page via Email Share this page via Stumble Upon Share this page via Digg this Share this page via Facebook Share this page via Twitter
Share