I’ve previously written about Kaplak’s multi-platform strategy and compared our business aspirations to the world of grafitti painting in our local neighbourhood. We want to create a company, which is capable of inviting “tags” and “shouts”, i.e. inputs from outside our company, so that we may, in the process and with time, learn how to do a great “piece”, so to speak. Inviting outside input is more difficult, than one would imagine, as everything in the business world as is, is built around keeping closed circles closed and creating stiff hierarchies, which are detrimental to the very kind of open, global process, we mean to help kick off and participate in. By all means, we want to steer clear of the corporate thickness, which quickly creeps into a company and prevents it from doing bold things.
Thus, we mean the “wiki way” in broader terms, than for just the work of building a wiki. We consider it a way of doing business and a mindset, which we need, in order to maintain a broad online presence over a number of different platforms and web architectures, without being overencumbered by the sheer vastness of what we’re doing – “making the world’s ends meet”, as we say, i.e. making financially viable connections between niche products and global niche markets.
Building and writing a blog sometimes can be like working against the clock. Posts are time-stamped and articles read and digested in the order they are published.
Not so with wikis. They evolve slowly over time, as additions to the wiki accumulate, from vastly different and otherwise territorially and contextually dispersed contributors. A wiki is built from time to time, when there’s something to add. A page can be an inactive dead end for months or even years, and it can see a sudden outburst of activity from one moment to the other, when it finds it’s use in a new context.
We understand and implement our online strategy much in this way. We use web tools and services, when they are useful to us, and we try to add bits and pieces to our network, when we need to. We don’t write blog posts every day, just for the sake of it or just to draw in traffic. However, we do work systematically to find explicit ways to add information or new contacts to our network. Precisely where the activity occurs – whether it happens on Twitter or Friendfeed, or somewhere else – is less important, as long as our pieces and nitbits are closely interlinked, and as long as we can feed stuff from one platform to another. The last thing is a high priority, which is why RSS and widgets are important. But what is even more important, is that in most contexts, not just in our wiki, we invite replies, comments, reactions, input, if just for the rare case, when someone in some unexpected context stumbles upon one of the bits and pieces, which help he or she activate that page and connect with us.