Ryan Wold ryanwoldatwork

Improving process-oriented culture in large organizations involves aligning the people, workflows, and tools to ensure consistent outcomes, adaptability, and efficiency. Below are some recommended books, articles, and authors that cover this topic comprehensively:

Books

"The Goal: A Process of Ongoing Improvement" by Eliyahu M. Goldratt
- A foundational book on process improvement and the Theory of Constraints.
- Explores how to identify and resolve bottlenecks in workflows.
"Lean Thinking: Banish Waste and Create Wealth in Your Corporation" by James P. Womack and Daniel T. Jones

we rely on the container for the context

how does the artifact itself have that

folksonomy taxonomy ontology

Business Process Models, because they are structured data, can answer business questions like:

Who are the Personas or Systems in a workflow?
What are all the Workflows for a Persona?
What are the steps in a Workflow?
What is the sequence of Events in a Workflow?
What are the Artifacts (documents/records) of a Workflow?
Which workflows does a System support?

Traditional, visual-only journey maps and service blueprints are useful,

public users
federal staffer (USA)
federal staffer (foreign)
foreign staffer
compliance officer
policy staffer
political stakeholder
standards body staffer (NIST)
product developer (implementer of auth/login solution)
vendor developer (developer of auth/login solution)

A key distinction I find a little hard to communicate is the difference between "just a list of things" to a "structured dataset".

Informal lists can be easy, but they tend to lack 1) structure and 2) governance - and because of this, these lists tend to get duplicated for many audiences, and thus 1) lose provenance 2) lack authority and 3) increase information glut or "noise".

https://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller acknowledges how managed "Model" data can be projected in multiple "Views" based on varying user needs.

What can somebody do to assist an open-source project in some way?

The general flow is something like the following.

(necessary) find or perceive an issue in a software application
(necessary) describe the issue in a way that's reproducable or recognizable, by creating an Issue in a project/repository
(optional) conceive of a fix for the issue
(optional) test that the fix actually works - by updating code in a dev console or in a local instance of the app, for example
(optional) submit the changed code fix as a Pull Request in the repo


	Process Management: Methods for Improving Products and Services, Eugene H. Melan, ASQC Quality Press 1992
	Improving Performance: How to Manage the White Space on the Organizational Chart, Geary A. Rummler and Alan P. Brache, Jossey-Bass, 1995
	Statistical Methods for Quality Improvement, Hotoshi Kume, The Association for Overseas Technical Scholarship, 1992
	Guide to Quality Control, Dr. Kaoru Ishikawa, Asian Productivity Organization, 1992
	Value Stream Mapping How to Visualize Work and Align Leadership for Organizational Transformation, Keren Martin and Mike Osterling, McGraw-Hill 2014
	Learning to See: Value-Stream Mapping to Create Value and Eliminate Muda, Mike Rother and John Shook, Lean Enterprise Institute, October 2009
	The Toyota Way: 14 Management Principles from the World’s Greatest manufacturer, Jeffrey K. Liker, McGraw-Hill, 2004
	Lean Six Sigma for Service: How to Use Lean Speed & Six Sigma Quality to Improve Services and Transactions, Michael L. George, McGraw-Hill, 2003
	Out of the Crisis, Deming,

	require 'open-uri'
	require 'json'
	require 'csv'

	api_key = "YOUR-API-DATA-GOV-API-KEY-THAT-IS-ALSO-ENTERED-IN-TOUCHPOINTS-GOES-HERE"
	url = "https://api.gsa.gov/analytics/touchpoints/v1/websites.json?API_KEY=#{api_key}"

	# Make the API request
	response = URI.open(url).read