{"action":"created","issue":{"url":"https://api.github.com/repos/holacracyone/Holacracy-Constitution/issues/89","repository_url":"https://api.github.com/repos/holacracyone/Holacracy-Constitution","labels_url":"https://api.github.com/repos/holacracyone/Holacracy-Constitution/issues/89/labels{/name}","comments_url":"https://api.github.com/repos/holacracyone/Holacracy-Constitution/issues/89/comments","events_url":"https://api.github.com/repos/holacracyone/Holacracy-Constitution/issues/89/events","html_url":"https://github.com/holacracyone/Holacracy-Constitution/issues/89","id":134395688,"number":89,"title":"simplified simplified language","user":{"login":"KoenVeltman","id":12639041,"avatar_url":"https://avatars.githubusercontent.com/u/12639041?v=3","gravatar_id":"","url":"https://api.github.com/users/KoenVeltman","html_url":"https://github.com/KoenVeltman","followers_url":"https://api.github.com/users/KoenVeltman/followers","following_url":"https://api.github.com/users/KoenVeltman/following{/other_user}","gists_url":"https://api.github.com/users/KoenVeltman/gists{/gist_id}","starred_url":"https://api.github.com/users/KoenVeltman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/KoenVeltman/subscriptions","organizations_url":"https://api.github.com/users/KoenVeltman/orgs","repos_url":"https://api.github.com/users/KoenVeltman/repos","events_url":"https://api.github.com/users/KoenVeltman/events{/privacy}","received_events_url":"https://api.github.com/users/KoenVeltman/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/holacracyone/Holacracy-Constitution/labels/refactoring","name":"refactoring","color":"fef2c0"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2016-02-17T20:49:39Z","updated_at":"2016-02-25T06:59:26Z","closed_at":null,"body":"What would a much simplified constitution read like? \r\n\r\nAn analogy I used before is with magnificent work like Adam Smith's \"Wealth of Nations\". Nowadays the economic concepts are pretty straight forward, but reading his initial work I found pretty incomprehensible. And it takes 100+ pages which is nowadays explained in a few chapters or paragraphs. \r\n\r\nThe Holacracy constitution (although existing for several years) is also relatively in an very early phase. And I dont want to disregard the amazing simplification already ongoing (e.g., from 4.0 to 4.1).\r\n\r\nWhat would a constitution read like when it is seasoned and aged? With its text just focused on people who truly understand it and live it.\r\n\r\nWhat I could imagine is that there is a very simple straightforward first 1-3 page section of the constitution that is sufficient for folks working fully with a self-managed mindset and equally supported environment. And a second section that contains all the further detail, caveats, counter-actions, or exceptions which you would only need at the start of an implementation or in abnormal situations (e.g., process breakdowns). \r\n\r\nAlternatively putting some of the details in appendixes could work (e.g., tactical/governance meeting processes, or the election steps). For the people \"in the know\" the sentence \"follow the set tactical and governance agenda's would just do fine.\r\n\r\nSorry to be a bit philosophical. Lets see if we get this one pragmatic. "},"comment":{"url":"https://api.github.com/repos/holacracyone/Holacracy-Constitution/issues/comments/188641427","html_url":"https://github.com/holacracyone/Holacracy-Constitution/issues/89#issuecomment-188641427","issue_url":"https://api.github.com/repos/holacracyone/Holacracy-Constitution/issues/89","id":188641427,"user":{"login":"KoenVeltman","id":12639041,"avatar_url":"https://avatars.githubusercontent.com/u/12639041?v=3","gravatar_id":"","url":"https://api.github.com/users/KoenVeltman","html_url":"https://github.com/KoenVeltman","followers_url":"https://api.github.com/users/KoenVeltman/followers","following_url":"https://api.github.com/users/KoenVeltman/following{/other_user}","gists_url":"https://api.github.com/users/KoenVeltman/gists{/gist_id}","starred_url":"https://api.github.com/users/KoenVeltman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/KoenVeltman/subscriptions","organizations_url":"https://api.github.com/users/KoenVeltman/orgs","repos_url":"https://api.github.com/users/KoenVeltman/repos","events_url":"https://api.github.com/users/KoenVeltman/events{/privacy}","received_events_url":"https://api.github.com/users/KoenVeltman/received_events","type":"User","site_admin":false},"created_at":"2016-02-25T06:59:26Z","updated_at":"2016-02-25T06:59:26Z","body":"again adding a simplification idea. another way to simplify is to separate articles that describe what you should do vs what you shouldn't do. In the early days of a holacracy adoption an organization probably benefits from reading explicitly you shouldn't do. But a few quarters/years down the road that is obvious to everybody. Just moving all the \"shouldnts\" to an appendix probably simplifies. For example the lines about that operational points cannot be recorded in governance meeting output"}}