What’s your future in OSS/BSS more closely linked to – elements of scarcity or abundance?
Did you notice that our previous article (What does the future hold for telco?) touched on scarcity and abundance in telco as well as how
“A swipe file is a collection of tested and proven advertising and sales letters. Keeping a swipe file (templates) is a common practice used by advertising copywriters and creative directors as a ready reference of ideas for projects. Copywriters are not the only ones who can benefit from having a swipe file.”
Wikipedia.
Do you keep swipe files as a ready reference of ideas for your OSS projects / operations?
They’re a record of what’s already worked, could be refined further or new ideas to test.
At an organisation level, swipe files help to accumulate and share knowledge. They’re otherwise known as knowledge bases, information management systems (IMS), wikis, etc. The challenge with these tools is in curating them, keeping them manageable and ensuring that great nuggets of wisdom continually get unearthed. Sometimes there is more effort allocated to maintaining them than is justified by the benefits they produce.
The key is ensuring that context is stored and indexed against (ie deriving feedback). For example, if a certain type of event comes up, the knowledge base not only has a record, but knows the context / history of similar events and can automatically recommend a set of actions to an operator. Without context and auto-prompting, the operator would have to choose to go searching for knowledge base entry that aligns with their current problem, not knowing whether a suitable entry even exists. Machine learning is definitely a target technology to help with this.
On a personal level, I use Evernote to store my swipe files, references and ideas. Many of my blog entries (including this one) start out as notes in Evernote. PAOSS.com itself forms a portfolio of swipe files that I regularly reference back to. The blog entries have not just the reference (eg the Wikipedia link above), but what I had in mind at the time and why it was relevant (ie the context and feedback).
I’d love to hear about how you search, store, reference and use your best OSS ideas (or if not yours, the ones you’ve swiped from elsewhere)…
BTW. I have no interests in Evernote. Nor does the reference to Evernote above generate any benefit to me (eg via affiliate links). It just happens to be what I use at the moment.
Did you notice that our previous article (What does the future hold for telco?) touched on scarcity and abundance in telco as well as how
Do you ever look into the past to determine whether commonalities / discrepancies could be used to inform how you might act into the future?
What’s your Everest? I was out doing a walk today and listening to a podcast (Jeff Lerner‘s “Unlock your Potential” with guest Colin O’Brady [episode #226]) and
Wait, “What??” I hear you ask! No it can’t. Have you ever worked on a BIG OSS project? One where the budget is in the
Here at Passionate About OSS, we are exactly that – Passionate About OSS (Operational Support Systems). We’re also passionate about BSS, NMS, or any other names you call the tools that help to operationalise your network.