{"id":2193,"date":"2026-11-19T01:50:00","date_gmt":"2026-11-19T01:50:00","guid":{"rendered":"https:\/\/devopsschool.org\/blog\/?p=2193"},"modified":"2026-11-19T01:50:00","modified_gmt":"2026-11-19T01:50:00","slug":"platform-team-learns-three-lines-case-story","status":"publish","type":"post","link":"https:\/\/devopsschool.org\/blog\/platform-team-learns-three-lines-case-story\/","title":{"rendered":"A Platform Team Learns Three Lines at a Time: A Case Story"},"content":{"rendered":"<p><em>A note before we begin: this team is imagined, built only to illustrate a working habit, and any likeness to a real one is accidental.<\/em><\/p>\n<p>Inside an online shop&#8217;s engineering group, a small platform team had a familiar problem. They were good at fixing things and bad at remembering how. Every quarter the same kinds of trouble resurfaced: a certificate that quietly expired, a deployment job that behaved differently in each environment, a handover that dropped a step. The engineers were capable and busy. What they lacked was a place where yesterday&#8217;s lesson could wait for next month&#8217;s task. This is the story of how a <strong>three-line lesson learned<\/strong> supplied one.<\/p>\n<h2>The trigger<\/h2>\n<p>It began after a long weekend release. The team lead, frustrated by a rollback that repeated an earlier one, asked a simple question in the retrospective channel: &#8220;Has anyone written down why this failed in March?&#8221; Silence followed. Someone found a chat thread from March, eventually, but it contained forty messages and no conclusion.<\/p>\n<p>The lead proposed an experiment for one month. After finishing any task longer than an hour, the person responsible would add three sentences to a shared page: the event, the takeaway and the change they would make. No review, no template beyond that, no approval.<\/p>\n<h2>The first month: awkward and short<\/h2>\n<p>The first entries were clumsy. One engineer wrote four lines. Another wrote &#8220;be more careful&#8221; as a third line, and the team lead gently pointed out that nobody could act on it. By the second week the standard emerged on its own: each line one sentence, and the third line a concrete action with a verb in it.<\/p>\n<p>When four weeks were up, the page held a few dozen notes. None was brilliant. Read together, though, they showed something the team had never seen so plainly. Three entries mentioned environment values set by hand. Four mentioned a handover where a step had been assumed. The page had turned scattered irritation into a visible list.<\/p>\n<h2>The second month: from notes to checks<\/h2>\n<p>At the start of the second month the team spent twenty minutes reading the page aloud. Two lessons repeated often enough to deserve action. The first became a line in the release checklist: compare environment values before go-ahead. The second became a short section in the handover template: state explicitly which steps the receiving person is expected to run.<\/p>\n<p>This is the moment when the habit stopped being a record and started being a process. The notes had earned their place by changing what the team did.<\/p>\n<h2>The quarter after: onboarding<\/h2>\n<p>Three months in, a new engineer joined. In previous years, onboarding had meant a week of questions and shadowing. This time the lead pointed the newcomer to the lessons page and suggested reading the last month of entries. The newcomer later said it was the most honest introduction to the team&#8217;s systems available, because it described real work, with real slips, in plain words.<\/p>\n<p>The newcomer also began adding entries at once, which was the lead&#8217;s quiet goal. Writing three lines on day three, even about something small like a confusing permission prompt, made the habit feel normal rather than imposed. Material for such growth is also found in guides on <a href=\"https:\/\/devopsschool.org\/blog\/devops-knowledge-gaps-students-must-fill-a-practical-guide\/\">knowledge gaps students must fill in DevOps<\/a>, which describe the kind of gaps a lessons page tends to expose in practice.<\/p>\n<h2>Evidence, such as it was<\/h2>\n<p>No study was run. The engineers simply noticed a handful of qualitative changes.<\/p>\n<ul>\n<li>Repeat problems became rarer, and when they happened, someone could usually point to the note that covered them.<\/li>\n<li>Release evenings were calmer, because checks derived from earlier notes caught common slips.<\/li>\n<li>Conversations about process became more specific. People cited entries rather than impressions.<\/li>\n<li>Estimates improved slightly, because the notes made recurring delays visible.<\/li>\n<\/ul>\n<p>None of this is proof, and the team would be the first to say so. It is simply what the engineers reported when asked.<\/p>\n<h2>The failures along the way<\/h2>\n<p>A fair case story includes the awkward parts.<\/p>\n<ul>\n<li>In the third month, notes thinned out during a busy launch. The lead restored the habit by writing three lines publicly after the launch and asking others to follow.<\/li>\n<li>Some entries were too vague. A short monthly review fixed this, since vague lines were easy to spot when read together.<\/li>\n<li>One person kept notes privately. Gently, the team agreed that a lesson nobody else can read cannot help anybody else.<\/li>\n<\/ul>\n<h2>The role of problem solving<\/h2>\n<p>Over the year, the team observed that the notes improved how they approached unfamiliar problems. Writing a second line, the &#8220;what did I learn&#8221; sentence, trained a habit of asking why before reaching for a fix. This echoes the ideas in the article on <a href=\"https:\/\/devopsschool.org\/blog\/devops-problem-solving-how-to-build-critical-thinking-skills\/\">sharpening critical thinking when solving DevOps problems<\/a>, where structured reasoning is treated as a skill that can be practised. Three lines, repeated, turn out to be one way of practising it.<\/p>\n<h2>A small addition: travel days<\/h2>\n<p>Several team members travelled to a conference during the year. One of them had been caught out by a missing data connection on arrival, and wrote it up in three lines: the flight landed late, the plan was not sorted in advance, and next time the connection would be arranged before departure. Others later consulted <a href=\"https:\/\/rankesim.com\/\">RankeSIM, a website that lets readers weigh local SIMs against travel eSIMs<\/a> ahead of their own trips, and added their own short notes on how it went. It was a minor episode, but it showed the habit spreading beyond the systems.<\/p>\n<h2>One year on<\/h2>\n<p>After twelve months the lessons page was long, searchable and, most importantly, used. New entries were typically short and specific. The team kept the three-line limit deliberately, resisting requests to add fields and categories. Their view was that the format&#8217;s greatest strength was how little it asked of anyone.<\/p>\n<h2>Takeaways from the story<\/h2>\n<ul>\n<li>Start with a one-month experiment and a tiny format.<\/li>\n<li>Make the third line an action with a verb.<\/li>\n<li>Read the notes together regularly and convert repeats into checks.<\/li>\n<li>Point newcomers to the page.<\/li>\n<li>Keep it public within the team, or it cannot help.<\/li>\n<\/ul>\n<p>If your own team is nodding along, the next task you finish is a fine place to try it.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A fictional case story of a platform team that began ending every task with a three-line lesson, and how its habits, reviews and onboarding changed over a year.<\/p>\n","protected":false},"author":5,"featured_media":2194,"comment_status":"","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[489],"tags":[],"class_list":["post-2193","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops-careers"],"_links":{"self":[{"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/posts\/2193","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/comments?post=2193"}],"version-history":[{"count":1,"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/posts\/2193\/revisions"}],"predecessor-version":[{"id":2297,"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/posts\/2193\/revisions\/2297"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/media\/2194"}],"wp:attachment":[{"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/media?parent=2193"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/categories?post=2193"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devopsschool.org\/blog\/wp-json\/wp\/v2\/tags?post=2193"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}