Closing chips is hard and it’s getting harder. As we discuss Pinpoint with people, we find that organizational memory is one of the pervasive problems in the industry.
We all have a limit for the amount of things we can keep in our head at one time. We remember the mistakes that we made most recently, but tend to forget the ones that haven’t bitten us in a while. This can cause problems when you close chips, managing ever increasing complexity, hoping you’ll remember all the various gotcha’s.
The more complex the chip, the more each engineer must specialize, creating unique solutions to unique issues. Passing this learning on to the team is very difficult.
Complexity also brings unexpected side effects. Just this last week, we heard a story of a team who spent a good deal of time putting in place clock gating for the whole chip. Things looked great until they pulled in the logic from the BIST module which introduced an extra 20,000 ungated flops into the design. It was a power nightmare.
Key problems facing teams go beyond the difficulty of tracking metrics. They must also make sure the entire team can see the effect of each member’s changes on the chip at large as well as provide a mechanism to capture organizational learning so that past mistakes are not repeated.
