Showing posts with label company information. Show all posts
Showing posts with label company information. Show all posts

December 09, 2010

Umair Haque puts out a great post about wikileaks. I'm quoting a chunk here. But read the whole thing.

Consider just how moribund yesterday's institutions are when it comes to information collecting and sharing. Take transparency in corporations. It's built on a set of institutions crafted in and for the industrial age — like annual and quarterly reports. Four times a year, boardrooms publish updates to their accounts, and once a year, a hefty report explaining and discussing them.

Now ask yourself: does that make even a tiny sliver of sense in a world where I can trade equities from nearly any beach in the world, hundreds of times a minute, using my iPhone? It's an obsolete institution, where my demand for information — to analyze, synthesize, and integrate — has vastly outstripped the capacity to supply it. Hence, stocks froth up and down before and after earnings report releases. When I can't get new information from the horse's mouth, I rely on your opinion, the latest rumor, or what talking heads are paid to say. Result: boom, crash, rinse, repeat. But the real question is one of institutional obsolescence. Why, for example, can't we have continuously updated earnings releases — that let us see what companies are earning in real-time — for a continuously connected world?

Sure: there's a balance to be struck between confidentiality and disclosure. But I'd argue that we're not even close to discovering it. Right now, yesterday's organizations — from corporations to Congress — have a gaping, yawning disclosure gap: the how, what, why, how and when of disclosure simply isn't good enough for markets and communities to be able to allocate and utilize resources productively or efficiently. That's why the traditional understanding of everything from GDP to "jobs" to "profit" to "IPO" is limited.

And the result of an undersupply of disclosure is toxic, perverse incentives. A CEO can make hundreds of millions for running a once-thriving company into the ground because he (or she) can earn his mega-bonus faster than you can stop him from earning it. And the systemic result of that is crisis, stagnation, and decline.

My guess is that, like updating GDP for the 21st century, real-time corporate reporting could create new markets, companies, and much-needed jobs. It might ignite novel sources of advantage — while of course creating disadvantage for companies who won't or can't play by its rules. But prosperity is always going to accrue to those who innovate yesterday's rusting, creaking institutions.



(BTW : my personal / political thoughts about wikileaks are on my other blog.)

November 16, 2005

Yellowikis

Aparently there's a wiki yellow pages for company information getting some publicity.

I have a personal interest here. I wrote a company registry module for Infoconomy back in 2000 (that site's running on Philip Greenspun's ACS). It was a good old-fashioned bit of relational modeling, handling international companies with HQs in different countries and multiple branches, categorization, partner and competitor relations etc.

When the site went live, the module was left out. No one, me included, could imagine that they'd launch with the small amount (around 50 companies skeletons, maybe 20 full profiles) of test data that had been entered during development. But researching, writing and entering the data was expensive. And this was a small startup magazine with a few journalists who realized that completing the catalogue was more work than they could handle.

Five years later, Infoconomy, and the CRM system (built by my friends on top of the ACS) seem to be still going strong. But, unless the company registry is hidden behind the subscription firewall, I don't think this feature ever did make it. Yellow-pages represent a great deal of work.

Can a wiki supplant that?

Here's what's good about a wiki. It's cheap. No one has to pay me to write a custom database application. If I was advising anyone who thought of building this kind of application, I'd start with a wiki as an internal prototype of the registry. I'd get them entering the data into wiki pages with some simple markup that could be scraped later.

I'm not quite prepared to stick my neck out and say I think Yellowikis will disrupt the yellow-pages industry. But I'd like to see it try.