I guess if people would ask at the same time that why aren't more Nokians actively involved in these forums and at the same time would read the general tone and respect level of the individual messages, for instance in this particular thread, you would perhaps see some hints of the potential conflict built within. i.e. semirandom people calling you incompetent based on some design detail does not really encourage you to actively participate in these discussions. Just as an observation. Hopefully I won't get flamed for this also.
Then again, for the actual issue. There was no usable tab component available for the designer (in this case me) to consider. The UI style guidance was to try to simplify the UI's, and one clear target for these was to clear out tabbed UI's, clear out split panel UI's as much as it is possible. Doing an exception for only one application wouldn't make sense in terms of UI consistency. Why could Call UI only do this and the other applications would not then do it. Sometimes overall UI consistency overrides the individual optimization you might want to do on some particular application.
"Just do the right thing" is something that it somewhat understandable from an outside perspective, because it allows the opinion holder to not care about the realities that were and are present for designing and implementing any feature within the device.
Hopefully nobody really thinks that the user would either select to buy this device or then leave it on the shop table would be dependent on whether there would be tabs on the missed calls list in the Call UI.
I'm personally a big fan of 37signals thinking in postings like these: http://gettingreal.37signals.com/ch05_Start_With_No.php http://37signals.com/svn/archives/000805.php The former talks essentially about saying no and shipping now vs. shipping in 2012 after saying yes too many times. The latter talks about "just do it" idealistic attitude of every feature you can think of vs. the reality of what saying yes to any feature actually means.