# Process knowledge vs state knowledge Process and state knowledge can be [[Tacit knowledge]] or [[Explicit knowledge]]. - Process Knowledge is knowing how things work, the steps to take, actions to perform to make something happen. Process Knowledge can be tacit: like a blacksmith knowing how to swing a hammer properly. But also explicit: like SOPs for sending a newsletter e-mail. - State Knowledge is knowing what the state of something is – the regulatory environment, or how a system is configured. Tacit State Knowledge: the blacksmith knowing when the iron has just the right temperature. Explicit State Knowledge: documentation how a system is configured. - Especially when designing systems for knowledge management it's extremely important to know what you're trying to design (for). Are you trying to formalize SOPs for a process, or document the state of a system? Or extracting knowledge about perceiving state correctly?