…can help garner user buy-in and help prioritize functionality that can deliver measurable process improvement…
The whole text is available only in print so I am unable to offer you a link. However, I am pretty sure you all have seen this kind of newspeak all over the place. Especially when browsing web sites of software vendors, the bigger ones being the heaviest offenders.
This is what I learned by reading Chris Pearson’s blog and noticing that there are no timestamps for articles and comments there. This goes against the standard practice and works perfectly. The reason is quite obvious after a closer look. Once you mark content with dates, it gets stigmatized. Instead of focusing on the merits of an article, readers start to judge it by the time it was published. Surely, something written two years ago has to be outdated, hasn’t it?
“The Rust Belt” will not take advantage of any kind of JavaScript or CSS hacks to look better in any particular browser. One Internet, one set of standards, one code. I am going to experiment with HTML5 elements that may be unrecognizable for some browsers so whatever the result is, it will not be corrected if browser-specific code is required.
A playing field for text, code and design, a personal (yet anonymous) notebook and whatever else it becomes in the future – that’s “The Rust Belt”. I am building it even now as I write, creating the structure and layout. Styling and graphics are to be the last two things to focus on. I want to get something out ASAP.