<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Current thinking — AEA by Ivory &amp; Co.</title><link>https://ivoryandcopartners.com/current-thinking</link><description>Evolving thinking and perspectives from Ivory &amp; Co. on AEA by Ivory &amp; Co.</description><language>en-AU</language><atom:link xmlns:atom="http://www.w3.org/2005/Atom" href="https://ivoryandcopartners.com/current-thinking/feed.xml" rel="self" type="application/rss+xml"/><item><title>Size is no longer the same as scale</title><link>https://ivoryandcopartners.com/current-thinking/size-is-no-longer-the-same-as-scale</link><guid isPermaLink="true">https://ivoryandcopartners.com/current-thinking/size-is-no-longer-the-same-as-scale</guid><pubDate>Wed, 18 Nov 2026 00:00:00 GMT</pubDate><dc:creator>Ivory &amp; Co.</dc:creator><description>Firms with fewer people can scale without the operational debt of a large workforce. A business needs to see its own architecture to modernise how it operates.</description><content:encoded><![CDATA[<p>A company with fewer people can now take on more of the market than it could when scale meant hiring. That is an observation from practice, not a finding from a survey. The firms that move fastest are often the ones that have not yet built a large workforce, a thick layer of management, and a stack of systems whose main job is to keep the people coordinated.</p><p>Larger organisations carry two kinds of weight. The first is operational debt: the processes, handoffs, approvals and local workarounds that accumulate because the business has been running for a long time. The second is the complexity of the workforce. Roles, managers, policies, and the work of keeping people aligned. Human capital management is not a side function in a large organisation. It is how participation in the work is arranged, and that arrangement is heavy. It is what size used to require.</p><p>Technology is one reason the pressure is rising. It is not the subject of the work. Work that once needed a department can now be carried by a smaller group, by software, or by a mix of people and systems, provided someone has been clear about the work itself: the roles, the people who fill them, how the work is performed, and who has authority to decide. Scale no longer lines up neatly with headcount.</p><p>This is where a firm with fewer employees has an advantage it did not used to have. It does not yet carry the operational debt. It does not yet have a workforce arrangement that has hardened around an older way of working. It can design the work, the roles and the reliance before the habits set. In practice, that is the difference between a business that grows by adding people to a tangle, and a business that grows because the work has been described well enough to be shared with systems and with a few people who know what they are responsible for.</p><p>The advantage is not automatic, and it is not a reason to stay small. A firm with fewer employees can also be opaque to itself. If the work lives in one or two heads, speed is borrowed, not built. The moment the person who holds the picture is the only one who can see how the pieces connect, the business has the same problem as the large one, just with less paperwork. What the smaller firm has is a chance to see its architecture before the debt arrives.</p><p>Larger businesses are not stuck, but they pay a higher price to change. Pulling them apart means tracing handoffs that nobody designed on purpose, roles that exist because a person was hired, and systems that remember a decision the business has since reversed. The workforce complexity is not abstract. It is leave, performance, managers, policies, and the question of who is allowed to do the work. Modernising the tools without modernising the people, the roles and the process leaves the weight in place. </p><p>Observed from the work, not from a forecast, the question scale asks has widened. It still asks how many people, and how to manage them. It also asks how the work is performed, which roles people fill, who has authority to decide, and what can be relied on. A business that can answer for its systems and not for its people and its process will look busy and still fall behind.</p><p>Every business going forward needs a strong understanding of its own architecture. Not a diagram of its systems, and not a diagram filed once. A working account of its strategy, its capabilities, how the work is performed, the roles and the people who fill them, who has authority to decide, and the relationships and conditions it depends on. Technology is one part of that account. It is not the account. That account is what lets a smaller firm scale without inheriting the complexity of a larger one, and what lets a larger firm take weight out instead of automating the tangle. AEA by Ivory &amp; Co. is that account, built by pulling real businesses apart and putting them back together. Ivory &amp; Co. stewards it. The conviction in it comes from the practice Josephine Otimi originated: a business that cannot see its own architecture will modernise its tools and leave its people, its process and its decisions where they were.</p><p>The practical test is ordinary. Take a change the business actually wants to make. Follow what it touches: the capability, how the work is performed, the roles and the people who fill them, who has authority to decide, and the conditions under which the result can be trusted. If that path can be walked from the record, the business understands its architecture well enough to modernise how it operates. If the path can only be walked by asking the person who remembers, the business is still carrying the complexity in the head of whoever happens to know. A new system will not remove that. It will multiply it.</p><p>This note is not a claim that small firms win, or that large firms cannot. It is an observation from two decades of building and advising. The firms that move are the ones that can see themselves. Headcount used to be a rough proxy for that capacity. It is a poor one now.</p>]]></content:encoded></item><item><title>A body of work</title><link>https://ivoryandcopartners.com/current-thinking/a-body-of-work</link><guid isPermaLink="true">https://ivoryandcopartners.com/current-thinking/a-body-of-work</guid><pubDate>Wed, 18 Nov 2026 00:00:00 GMT</pubDate><dc:creator>Ivory &amp; Co.</dc:creator><description>Ivory &amp; Co. publishes AEA by Ivory &amp; Co. as a body of work: the standards, the research, and the distinctions that keep an enterprise intelligible.</description><content:encoded><![CDATA[<p>Ivory &amp; Co. publishes AEA by Ivory &amp; Co. as a body of work. The standards, the research, and the distinctions that keep an enterprise intelligible are the work. They are not a product release, and they are not a record of software versions.</p><p>This page is where the institution sets down a perspective while it is still being examined. A note here can be revised. What has been established stays in the standards, under its own version. What is still being considered can be read here.</p><p>The credit for that thinking is Ivory &amp; Co. The work is the subject, not a person.</p>]]></content:encoded></item></channel></rss>