{"id":26,"date":"2026-09-15T09:28:46","date_gmt":"2026-09-15T09:28:46","guid":{"rendered":"https:\/\/markjust.com\/index.php\/notes\/systems-should-remove-work-not-add-another-screen\/"},"modified":"2026-09-15T09:28:46","modified_gmt":"2026-09-15T09:28:46","slug":"systems-should-remove-work-not-add-another-screen","status":"publish","type":"mj_note","link":"https:\/\/markjust.com\/index.php\/notes\/systems-should-remove-work-not-add-another-screen\/","title":{"rendered":"Systems should remove work, not add another screen"},"content":{"rendered":"<p>The best internal tool is not the one with the most features. It is the one that removes duplicated decisions, manual handovers and hidden state.<\/p>\n<p>I tend to start with the workflow: who needs to know what, when, and what should happen next. The technology comes after that.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A short principle behind the way I build operational software.<\/p>\n","protected":false},"featured_media":0,"template":"","class_list":["post-26","mj_note","type-mj_note","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/markjust.com\/index.php\/wp-json\/wp\/v2\/mj_note\/26","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/markjust.com\/index.php\/wp-json\/wp\/v2\/mj_note"}],"about":[{"href":"https:\/\/markjust.com\/index.php\/wp-json\/wp\/v2\/types\/mj_note"}],"version-history":[{"count":0,"href":"https:\/\/markjust.com\/index.php\/wp-json\/wp\/v2\/mj_note\/26\/revisions"}],"wp:attachment":[{"href":"https:\/\/markjust.com\/index.php\/wp-json\/wp\/v2\/media?parent=26"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}