Which gives me a great reminder -- thanks for the hint.
Years in business. Seems like a great shorthand way of explaining something to the reader. However, as the saying goes, some businesses haven't been doing business for 12 years ...they've been repeating the same first year in business a dozen times over.
How refreshing it would be for someone to sit you down and explain exactly what a seasoned professional knows that rookies don't. Years in business is a feature. The benefits are...
...You don't get fooled by short-term fads (useful in financial services)
...If you do work in teams, time in business can mean your teams actually know how to collaborate. How many times have you seen "teams" which were just a group of people thrown at a problem, or client?
....If you're in the technology field, you can champion useful advances. Zeldman writes how many web developers resisted the standards movement he pioneered, in the beginning. In a similar way you can be in business for a dozen years, resisting every inevitable trend in the business. Or you can talk about what you see as valuable advances and how you adopted some, passed on others and why.
My guess? Zeldman would have had less resistance if he had gone out of his way to explain the benefits, and not merely the features of standards. Not just to developers, but to the clients of those developers.
To relate this point back to the CSS example, you might talk about experience by contrasting CSS longhand with CSS shorthand.
In the early days of the Geek Squad, the business faced resistance from IT departments. In response, they created "stealth mode" operations and policies -- purely a face saving measure for the Geek Squad to get the billable, while the internal IT department takes the credit.
That's something even some technology consultants with twenty years in business have yet to fully understand. And it's not something you understand when the ink is still drying on your 'certs.'
In other words years in business is the feature -- an explanation or demonstration of what you learned over those years is the benefit. If the topic is CSS code, then give examples of code. If the topic is features and benefits, give examples of a feature then explain how you translate it into a benefit.
That's the point of a "clinic" type thread.