Dion Hinchcliffe has a very interesting post entitled Eleven Emerging Ideas for SOA Architects in 2007. I really like Dion's list, particularly the idea of SOA being enabled more directly to the user. He suggests that making services consumable in the browser (via REST or similar), making AJAX the face of your SOA, providing access to SOA services via widgets. In other words, he's recommending starting to externalize SOA in different ways more directly to the end user. This is an idea for which I'm very much in favour.
He also mentions the statistic that 48% of CIOs will be looking to actually start using their SOAs to connect to external partners this year.
This gives me hope. We've spent the last 2-3 years building architecture and communicating SOA, followed by our first real SOA/EA based projects. We're just now reaching a place where we'll have services available internally, and ready for the acid tests of reuse (let's see). In my opinion, it's taken about 3 years for us to be poised to be seriously considering extending/exposing portions of our SOA in various ways. The 48% stat makes me think we're in a good place on the curve, particularly for a small organization.