Week in Workflow: Event-Driven Process, Analytics
Here are some of the interesting things the Fulcrum team has found from around the web related to workflow, data, and analytics. Enjoy!
First up is a great, brief post from Tomasz Tunguz of Redpoint Ventures. He argues that the old data workflow model saw businesses buying software → doing work → updating databases → creating reports. He describes a new model where events and triggers drive and optimize the work process being done, which “prioritizes and informs” their work to be more effective. This is already being done in many markets, of course. Event-driven systems are expanding. Better outputs, less work.
The team from Metabase describes two primary workflows for analysts: “Pushing important data to them, or letting them chose when and what data to Pull on their own”. Pull is great for small teams looking to self-serve specific needs; push is better for company-wide data points to be recursively analyzed (think weekly status reports).
Brad Kirn from Astronomer talks about their path to becoming a better data-driven company. It’s not just about collection, which is where many organizations start and stop. It means nothing if you don’t do anything with it.
The awesome group at ZenHub (we’re huge fans at Fulcrum) have published this excellent e-book on how you can use GitHub for project management, not just code collaboration. Chock full of tips and tricks for anyone that uses GitHub heavily for team collaboration, like we do.