Wide Labels

I ended last week’s post with the view that removal of labels and building in the intent and components of these labels into an organisation’s processes might result in structure better than one obtained by a piecemeal approach. I’m still thinking about Surekha’s last comment – on corporate governance, and wondering whether it does indeed encompass (enough) the social facet. Social, both in terms of implication on the larger society, as well as the social used in the context of say, social media.

While I’m not expert enough to look at the first part comprehensively and offer the soundest of opinions, I think the latter is everyone’s playground ๐Ÿ™‚ On that front, I don’t think corporate governance quite makes the cut. And that led me to keep searching for various models being discussed. I also brought into this search the perspective I’d shared earlier on a Dunbar’s number for brands/organisations, retaining the ‘soul of the brand’ (courtesy Chris Brogan) and scalability issues.

And that’s how I came across the ‘Platform Organisation’ concept. The presentation below approaches the need for this from a communication perspective

The larger organisational imperative can be read here. This worked for me because I thought it matched business and social needs.ย  The community would ensure the soul of the brand is intact and would also allow a ‘scaling up’ of the brand’s Dunbar number. But I did wonder whether this would work for large organisations thatย  have a legacy of systems and processes. Deciphering that would perhaps be the next logical step.

As I’ve always maintained, the business structures we have built have a huge impact on how we live and consume as a society, and the lives we lead as individuals,(an old and favourite read discovered via Dina) and hence the extended interest on this topic stream. ๐Ÿ™‚

until next time, life’s work ๐Ÿ™‚

PS: While on the subject, a related good read via @vijaysankaran “The Definitive Guide to Scaling Social Enterprise

Leave a Reply

Your email address will not be published. Required fields are marked *