top | item 46906338

(no title)

crashabr | 24 days ago

Would you be able to share more? I lead a tiny non-profit org doing data literacy mentoring and I've been meaning to move more of our process docs to Logseq. Although I probably don't need a tool of the level of sophistication of usm.tools, I could take inspiration from your core ideas for our homegrown system.

discuss

order

kukkeliskuu|23 days ago

To understand the approach, you need to first understand the method it is based on.

I have written a simple introduction about it that you can download for free from simpleusm.com, no sign-up required.

Simple homegrown system for processes is not that difficult to do. You basically model the USM process model, templates as instances which you then copy as a basis for editing and make a UI around the editing.

You could even just use JSON files and git, but while the data model is not complex, it is still not simple enough for editing by hand in an editor.

Then the question is what is the benefit. I would say that just using USM to define your services is helpful.

By this approach you can build various stakeholders views to your services that are always up to date and do not require manual labor.