<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Coder-Framework on Framework Made Simple</title><link>https://framework.metacog.co.kr/tags/coder-framework/</link><description>Recent content in Coder-Framework on Framework Made Simple</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 07 Aug 2026 05:46:47 +0900</lastBuildDate><atom:link href="https://framework.metacog.co.kr/tags/coder-framework/index.xml" rel="self" type="application/rss+xml"/><item><title>CODER: Five Questions That Turn Any Problem Into a Plan</title><link>https://framework.metacog.co.kr/posts/2026-08-07-coder-framework-context-ownership-decision-effect-reflection/</link><pubDate>Fri, 07 Aug 2026 05:46:47 +0900</pubDate><guid>https://framework.metacog.co.kr/posts/2026-08-07-coder-framework-context-ownership-decision-effect-reflection/</guid><description>&lt;h2 id="-what-is-it"&gt;🔍 What Is It?&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;It&amp;rsquo;s a five-step thinking loop that helps you understand what&amp;rsquo;s going on, decide what to do, see what happens, and get a little smarter every time you repeat it.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;CODER is a five-step thinking tool that grown-ups use whenever they face a problem, make a decision, or run a project. Each letter stands for one question you answer in order: What is the situation? Who is responsible? What are we going to do? What happened when we did it? What did we learn? Working through them in order stops people from jumping straight to solutions before they even understand the problem.
The first two steps — Context and Ownership — are all about setting up clearly before anyone acts. Context means reading the room: what is already true, what is missing, and why this matters right now. Ownership means naming who is in charge of each piece, so nothing slips and nobody can say &amp;ldquo;I thought they were handling that.&amp;rdquo;
The last step, Reflection, is what turns CODER from a simple checklist into a loop. After you see the Effect of your decision, you sit down honestly and ask: what worked, what did not, and what would we change? That answer becomes the new Context at the very start of the next cycle, so the team gets a little wiser every single time around.&lt;/p&gt;</description></item></channel></rss>