Thirty days is enough to understand the current system, test one meaningful improvement, and establish a useful review rhythm. It is not enough to redesign everything, which is precisely why the boundary encourages focus. Knowledge management makes useful context easy to capture, find, trust, and improve as part of normal work.
Week one: understand reality
Repositories become archives when publishing is burdensome, ownership is unclear, and information is organized around departments rather than questions. Begin by observing the work as it happens and separating symptoms from the conditions that repeatedly create them.
Collect the questions people repeatedly ask and make their trusted answers easier to find than asking again. Speak with the people who perform the work, receive its output, and handle its exceptions so the current picture reflects reality rather than policy alone.
Weeks two and three: test a better way
Capture the emerging approach in a knowledge map with audience-based navigation, page owners, freshness signals, and contribution paths. The artifact should make the next decision easier, not become documentation maintained for its own sake.
Keep the first change small enough to reverse and specific enough to evaluate. Give one person clear ownership, make constraints explicit, and agree on when the team will inspect the result.
Week four: decide what to sustain
Use search success, reuse, freshness, repeated questions, and time to answer to understand progress from more than one angle. A measure belongs in the review only when a meaningful change would prompt a question, decision, or action.
End each review by recording what the team learned, what it will change, and what remains uncertain. Durable improvement comes from repeating that loop with discipline rather than launching a larger program.
