4 ms·
At $DAY_JOB we have various document (or rather, knowledge) repositories -- a mostly-abandoned-but-still-useful-often-enough-to-not-ignore wiki, the obligatory
by Jedd 11y ago
At $DAY_JOB we have various document (or rather, knowledge) repositories -- a mostly-abandoned-but-still-useful-often-enough-to-not-ignore wiki, the obligatory but overwhelming salesforce, personal (silo) collections of email lists/archives, a semi-public knowledge base, a half-hearted attempt at moving internal mail lists into yammer, various product guides (PDF's), a public-access user forum, an LMS, and probably a few others I don't know about. It is precisely as easy to search for information as you'd assume.
Last year we embraced Sharepoint - with expectations of replacing much of the above. (It didn't.)
Evidently no one uses Sharepoint as a way of presenting documentation to the world - let alone using the wiki-like features - not even Microsoft. What's the opposite of NIH syndrome?
- mavhc 11y agoSituation: There are 14 competing information stores. 14?! Ridiculous! We need to develop one universal store that covers everyone's use cases. Situation: There are 15 competing information stores.
- alblue 11y agoObligatory XKCD reference for above: https://xkcd.com/927/ https://xkcd.com/927/
- rtpg 11y agoSolution: Move things over from one into the blessed solution, and then kill the other one. Repeat as necessary. Accept that nothing will cover 100% Sometimes you have to push to fix the process
- hvidgaard 11y agoYou always have to push to make changes like this. You have to allocate ressources to migrate, and while it may save money in the long run, not all management people understand or want to pay for it.
- brazzledazzle 11y agoQuite often the only push that can fix problems like this is push from upper management because no matter what someone is going to be upset and will sabotage or drag it out forever.
- tallanvor 11y agoA lot of companies do use SharePoint that way (including Microsoft), they just heavily modify the look, and in some cases (Microsoft kb articles, as an example) have publishing flows to export static pages to be cached by CDNs.
- Jedd 11y agoI don't doubt some do this - I don't know how you'd tell from looking at a (heavily skinned) site. But it sounds like MS hasn't done this here - they've designed and built a new documentation repository. More power to them, btw. Most (HN) people's complaints sound fairly cosmetic - easy enough to adjust. Sensible URL's are probably worth the cost of conversion alone. But my point is/was that this doesn't appear to be a re-skinning of Sharepoint - it looks like (yet another) bespoke DMS.
- tobyjsullivan 11y ago> our existing content infrastructure TechNet and MSDN... are built on a 10-15 year-old brittle codebase I just assumed they meant Sharepoint there.