<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.durantlaw.info" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>systems</title>
 <link>http://www.durantlaw.info/taxonomy/term/433</link>
 <description>The taxonomy view with a depth of 0.</description>
 <language>en</language>
<item>
 <title>System Boundaries</title>
 <link>http://www.durantlaw.info/System+Boundaries</link>
 <description>&lt;p&gt;
In the last 15 years in Australia public-sector organisations have been down-sized, right-sized, reorganised, restructured, united, bisected, and sometimes like Defence are now up-sizing! All have had grand visions, strategic business plans, roadmaps, outsourcing plans and so on. Most of these initiatives have failed to realise the expected efficiencies or significantly improve competence. Why?
&lt;/p&gt;
&lt;p&gt;
I think the leaders of these organisations wish for simplicity even when it is not possible to avoid inherent complexity. In particular they put in place piecemeal business solutions and fail to recognise they are part of a wider system. In short they don’t understand their system boundaries or their cross boundary relationships, and don’t give the change initiative time to work before embarking on another. I think many public-sector organisations would benefit from a &lt;a href=&quot;http://en.wikipedia.org/wiki/Systems_thinking&quot; target=&quot;_blank&quot;&gt;systems thinking&lt;/a&gt; approach to management. ...
&lt;/p&gt;


&lt;p&gt;&lt;a href=&quot;http://www.durantlaw.info/System+Boundaries&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.durantlaw.info/System+Boundaries#comments</comments>
 <category domain="http://www.durantlaw.info/taxonomy/term/433">systems</category>
 <pubDate>Mon, 22 Oct 2007 16:35:38 -0400</pubDate>
 <dc:creator>graham durant-law</dc:creator>
 <guid isPermaLink="false">2349 at http://www.durantlaw.info</guid>
</item>
<item>
 <title>The RAAKERS™ Framework</title>
 <link>http://www.durantlaw.info/RAAKERS+Framework</link>
 <description>&lt;p&gt;
In my 30 years of work in or around public service departments I have noted that seven attributes must be in alignment for an organisation to be effective. (Note I didn’t say efficient, which will be the subject of another blog). They are responsibility, authority, accountability, knowledge, experience, resources and systems, which I call the &lt;em&gt;RAAKERS™ Framework&lt;/em&gt;.
&lt;/p&gt;
&lt;p&gt;
The first three attributes - responsibility, authority, and accountability – are essential for individual and organisation success. Too often I see people given the responsibility for an outcome, but they don’t have the organisational authority to make it happen, or worse still are not accountable even if they have the authority. I have also seen the paradox where a sub-department is accountable for a series of outcomes, but doesn’t have the authority or agreement to implement them in other sub-departments, and so is not responsible for the foreign sub-department implementation. Equally one can be responsible to implement an outcome, but not have the authority to implement it, and ultimately not be accountable for the success or failure of the initiative. Task and outcome success are therefore dependent on responsibility, authority and accountability alignment, both at the individual and organisational level. ...
&lt;/p&gt;


&lt;p&gt;&lt;a href=&quot;http://www.durantlaw.info/RAAKERS+Framework&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.durantlaw.info/RAAKERS+Framework#comments</comments>
 <category domain="http://www.durantlaw.info/taxonomy/term/423">knowledge</category>
 <category domain="http://www.durantlaw.info/taxonomy/term/422">knowledge management</category>
 <category domain="http://www.durantlaw.info/taxonomy/term/428">knowledge management model</category>
 <category domain="http://www.durantlaw.info/taxonomy/term/433">systems</category>
 <pubDate>Mon, 15 Oct 2007 02:26:01 -0400</pubDate>
 <dc:creator>graham durant-law</dc:creator>
 <guid isPermaLink="false">2339 at http://www.durantlaw.info</guid>
</item>
<item>
 <title>My links</title>
 <link>http://www.durantlaw.info/Links</link>
 <description>&lt;h3&gt;Introduction&lt;/h3&gt;
&lt;p&gt;
This page contains a list of links to sites that I find interesting or useful.  It is arranged alphabetically and is grouped according to my interests.
&lt;/p&gt;


&lt;p&gt;&lt;a href=&quot;http://www.durantlaw.info/Links&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.durantlaw.info/Links#comments</comments>
 <category domain="http://www.durantlaw.info/taxonomy/term/9">bagpipes</category>
 <category domain="http://www.durantlaw.info/taxonomy/term/434">complexity</category>
 <category domain="http://www.durantlaw.info/taxonomy/term/422">knowledge management</category>
 <category domain="http://www.durantlaw.info/taxonomy/term/4">network analysis</category>
 <category domain="http://www.durantlaw.info/taxonomy/term/433">systems</category>
 <pubDate>Sun, 10 Jun 2007 06:20:34 -0400</pubDate>
 <dc:creator>Graham Durant-Law</dc:creator>
 <guid isPermaLink="false">9 at http://www.durantlaw.info</guid>
</item>
<item>
 <title>Organic Whole</title>
 <link>http://www.durantlaw.info/node/2477</link>
 <description>&lt;p&gt;It may have been possible in the past, for things to have happened in isolation, but from this time forth, the world must be seen as an organic whole, everything affects everything&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Polibius&lt;/EM&gt;&lt;/p&gt;
</description>
 <comments>http://www.durantlaw.info/node/2477#comments</comments>
 <category domain="http://www.durantlaw.info/taxonomy/term/4">network analysis</category>
 <category domain="http://www.durantlaw.info/taxonomy/term/433">systems</category>
 <pubDate>Tue, 20 May 2008 03:52:09 -0400</pubDate>
 <dc:creator>graham durant-law</dc:creator>
 <guid isPermaLink="false">2477 at http://www.durantlaw.info</guid>
</item>
<item>
 <title>Networks, Hierarchy and Organisations</title>
 <link>http://www.durantlaw.info/node/2434</link>
 <description>&lt;p&gt;Hierarchy adapts knowledge to the organization; a network adapts the organization to the knowledge.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;George Siemens&lt;/em&gt;&lt;/p&gt;
</description>
 <comments>http://www.durantlaw.info/node/2434#comments</comments>
 <category domain="http://www.durantlaw.info/taxonomy/term/434">complexity</category>
 <category domain="http://www.durantlaw.info/taxonomy/term/4">network analysis</category>
 <category domain="http://www.durantlaw.info/taxonomy/term/433">systems</category>
 <pubDate>Fri, 01 Feb 2008 22:05:47 -0500</pubDate>
 <dc:creator>graham durant-law</dc:creator>
 <guid isPermaLink="false">2434 at http://www.durantlaw.info</guid>
</item>
<item>
 <title>Holon</title>
 <link>http://www.durantlaw.info/node/2275</link>
 <description>&lt;p&gt;A holon is an identifiable part of a system, or a system in its own right, which has a unique identity yet is made up of subordinate parts and in turn is part of a larger whole. A holon exhibits both autonomous and cooperative behaviour, and can combine to form another holon, thus forming a hierarchy called a holarchy.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Arthur Koestler&lt;/em&gt;&lt;/p&gt;
</description>
 <comments>http://www.durantlaw.info/node/2275#comments</comments>
 <category domain="http://www.durantlaw.info/taxonomy/term/434">complexity</category>
 <category domain="http://www.durantlaw.info/taxonomy/term/433">systems</category>
 <pubDate>Mon, 18 Jun 2007 22:06:17 -0400</pubDate>
 <dc:creator>Graham Durant-Law</dc:creator>
 <guid isPermaLink="false">2275 at http://www.durantlaw.info</guid>
</item>
<item>
 <title>Many rivers to cross: from ICT to knowledge management systems</title>
 <link>http://www.durantlaw.info/node/1958</link>
 <description></description>
 <comments>http://www.durantlaw.info/node/1958#comments</comments>
 <category domain="http://www.durantlaw.info/taxonomy/term/422">knowledge management</category>
 <category domain="http://www.durantlaw.info/taxonomy/term/428">knowledge management model</category>
 <category domain="http://www.durantlaw.info/taxonomy/term/433">systems</category>
 <pubDate>Sun, 17 Jun 2007 07:46:44 -0400</pubDate>
 <dc:creator>graham durant-law</dc:creator>
 <guid isPermaLink="false">1958 at http://www.durantlaw.info</guid>
</item>
<item>
 <title>Soft systems strategy: rationale, case study and theory development</title>
 <link>http://www.durantlaw.info/node/2152</link>
 <description></description>
 <comments>http://www.durantlaw.info/node/2152#comments</comments>
 <category domain="http://www.durantlaw.info/taxonomy/term/434">complexity</category>
 <category domain="http://www.durantlaw.info/taxonomy/term/7">research</category>
 <category domain="http://www.durantlaw.info/taxonomy/term/433">systems</category>
 <pubDate>Sun, 17 Jun 2007 07:46:44 -0400</pubDate>
 <dc:creator>graham durant-law</dc:creator>
 <guid isPermaLink="false">2152 at http://www.durantlaw.info</guid>
</item>
<item>
 <title>The philosophical foundations of software engineering</title>
 <link>http://www.durantlaw.info/node/1707</link>
 <description></description>
 <comments>http://www.durantlaw.info/node/1707#comments</comments>
 <category domain="http://www.durantlaw.info/taxonomy/term/433">systems</category>
 <pubDate>Sun, 17 Jun 2007 07:46:44 -0400</pubDate>
 <dc:creator>graham durant-law</dc:creator>
 <guid isPermaLink="false">1707 at http://www.durantlaw.info</guid>
</item>
<item>
 <title>Putting systems to work</title>
 <link>http://www.durantlaw.info/node/1966</link>
 <description></description>
 <comments>http://www.durantlaw.info/node/1966#comments</comments>
 <category domain="http://www.durantlaw.info/taxonomy/term/434">complexity</category>
 <category domain="http://www.durantlaw.info/taxonomy/term/433">systems</category>
 <pubDate>Sun, 17 Jun 2007 07:46:44 -0400</pubDate>
 <dc:creator>graham durant-law</dc:creator>
 <guid isPermaLink="false">1966 at http://www.durantlaw.info</guid>
</item>
</channel>
</rss>
