Great job. Son of meeting minutes.

The Product Management Council met this morning and had a productive discussion of the current enterprise projects.  Budget concerns have had some restraining effect on their progress.  We will hold a meeting later this month to kick off the business.utah.gov project.  The live chat/response pilot is continuing and we will give product managers access so they can begin to get ideas for how to use it.  Rick Leimbach, the product manager for the Tax Commission gave a nice briefing on how Tax is using metrics to monitor the success of the Renewal Express system including an analysis of how many people begin the process without completing it.  They are also using their metrics to design marketing programs that will increase the utility of their online solutions.  Currently, some agencies are using Webtrends, while there are others who are still not measuring anything.  We will do a presentation on metrics tools and work on an enterprise program to measure adoption rates in the near future.  Management services are part of the web hosting environment that ITS supports.  Utah Interactive provides similar services for the applications that they are hosting.  Here's a presentation given at Fedweb that gets at some of the issues. 

This reads a lot like a programme management office. Great to see such practices. Very cool to be blogging it.

If all the attendees blogged the meeting, how would that change the experience? How would it change the next meeting?

Should each new product under management have its own blog category/channel?

Dave Winer reports a new "Radio" feature: Proxy Exceptions. This opens up intranet ftp sites and RSS feeds when I tell Radio to ignore my org's proxy service for servers on an exception list

Excellent for klogging!

Now I want more:

1. Let me share/publish my exceptions list. Perhaps as an opml file? An RSS file?
2. Let me subscribe to one or more exceptions lists.
3. Let me publish an aggregated exception list combined from my own entries and my subscriptions.
4. Autodetect urls that don't have a known top level domain (.com, .uk, etc.). Perhaps confirm with the user that it isn't a typo. Ask if I want to add this server to my exceptions list.
5. Validate that exceptions can still be reached and found.

[aka Blue Sky Radio]