They're an employee-owned, private company in one of the most low margin and cut-throat industries around. Both their profit and effect on the competition is incredible. Also, their management to worker ratio. ;) It would be interesting to see tech companies adopt a model like this. The results could be exciting to watch and maybe lead to more job security as well given every other kind of company likes to sell out.
Exactly. Likewise, their stores had 400 workers and 2 managers. Most retail workers I know say their company keeps staff too low to get the job done while having way too many managers with micromanagement. One of the top chains local store recently had only 2 stockers per fast moving department with about 40 managers auditing and coaching them on best practices. Walmart and Target employees told me they had similar issues but not as extreme effect.
So, as dredmorbius says, they have managers that pick good employees, give them incentives, show them justifiable best practices, listen to feedback, and otherwise stay out of the way. And the management works for the employees, who are the shareholders, not Wall St. Results: highest profit in industry, highest customer satisfaction, one of highest retention, and little risk in operation. IT startups should copy this if they're not just about selling out.
I had never heard of that minus the self-organizing teams concept. I'll have to read more on the subject, esp empirical data, before I can answer such a question. Thanks for the link and bringing it to my attention!
The co-op structure is interesting but it's ultimately constrained by the members'/employees' financial resources to contribute capital. That's why co-ops are always modest businesses like grocery stores, or a co-op of cleaning people, or in this article's case, a co-op of IT techs.
If you want to start a capital-intensive business like Google Inc or SpaceX, you have to use the typical corporate structure because you need the $X million in investments from angels, VCs, and the stock market.
The typical employees don't have a million dollars in their bank accounts to pool together and launch a Google-sized business as a co-op. The enormous costs for rack servers and data centers to scale out would outpace the employees' tiny cash contributions.
> The co-op structure is interesting but it's ultimately constrained by the members'/employees' financial resources to contribute capital.
Not quite true. Its constrained -- pretty much by definition -- to internal source of equity-based financing, but it can get external non-equity financing.
> That's why co-ops are always modest businesses like grocery stores, or a co-op of cleaning people, or in this article's case, a co-op of IT techs.
I don't know that I'd describe Mondragon corporation as a "modest business".
OTOH, they are usually by design fairly moderate-risk businesses, as their aren't many established financing instruments (or financiers providing them) suitable for high-risk coop ventures.
More typically a co-op will raise funds from members via shares. I'm a bit shaky on specifics, but those shares may be capable of being sold back (to the co-op as a whole). Voting righs often _don't_ accrue per share.
Debt financing, as mentioned, is another alternative.
The problem with that is there are tax implications to giving someone a chunk of a company (it's technically income), even if it is completely illiquid. Tax implications the employee probably can't afford much better than a buy-in.
coops normally have special status to get round some of these issues.
And coop members can have direct or indirect ownership a full on worker coop normally has direct ownership and organizations like John Lewis have indirect ie shares held in trust.
This article is "OK", but their example is a 4 person co-op, which makes you think that all co-ops like the food co-ops you see in college towns.
There are actually multiple forms of co-ops. Typically capital does come from the members (whether they be companies or individuals), but it could also come in as debt i.e. from a bank.
>Ace Hardware is a retailer-owned cooperative. Where the franchise board is owned by the member franchises.
The Ace Hardware franchise requires ~$1 million[1] in startup costs to open a store and be part of the "co-op". Most employees don't have that kind of money and they don't have the collateral to secure a $1 million loan from the bank. When the ticket for admission into the "co-op" costs $1 million, that's not the type of co-op people are discussing. The REI stores co-op is also not a good example of what workers are thinking about. REI is not employee-owned.
I think we need to level-set. When threads pop up about cooperatives, the driving sentiment is from typical workers/employees who don't like the corporate ownership structure (founder has equity worth millions/billions, and/or CEO is drawing $500,000+ salary, etc).
Therefore, the co-op structure where all employees are also the owners and share the profits looks very attractive. The problem is it will end up being a modest business. E.g. a cooperative of IT consultants. The IT Consultants Co-Op don't need members to contribute $1 million each to capitalize the business; they just start billing clients right away. They can pool their modest funds from their hourly billings to buy the shared office a laser printer and a coffee machine.
It would be great if a cutting edge big company (like Google, Amazon, or SpaceX) with ambitious and very expensive goals (driverless cars, drone delivery, Mars colony) could be "employee-owned" but it can't. Employees don't have the money.
See my comment and article about Publix. It can happen but requires management to have that vision to begin with. Thing is, most have never heard of this stuff working and wouldn't even consider it. Past that, there's the whole angle of "let's get rich owning our own company and selling out our workers later." But, get word out about the successes, then we might get more of them. And maybe I'll be lucky enough to work for one. :)
This is actually something I'm actively working on in my area, where there are a number of independent small tech consulting companies (most of them with just one employee), all with different niches and skillsets, and none of whom have offices or shops.
So everyone already has their own client base. The goal is to share some work, leverage eachothers' skillsets, and share a common space with inventory and a shop setting where you can meet customers in a professional environment.
The downside is that everyone's pretty independent-minded so it's a bit like herding cats. But the upside, if it works, will be pretty great for everyone involved.
If this is such a good way to run a tech company, why isn't it also a good way to develop software? In other words, why are projects led by BDFLs like Linux and Python so successful, while the design-by-committee approach is usually regarded as producing substandard outcomes?
Depends on the committee. The Ada designers, acting on committee's needs, came up with pretty much what they wanted. Had performance, availability and pricing issues that kept it from taking off as much as it could. Yet, the language's features accomplished their goals very well as proven by a number of empirical studies by military and defense contractors.
So, that's one success story. Anyone have any other examples? I'm asking because I really think this recurring theme is a myth about committee-design languages where the problem really is a prevalence of bad committees.
Tech coops are a new thing really as an ex poptel member that is news to me :-)
Though you might have thought that a politically aware organisation which all coops are would know what Al Jazeera's line was in running this story - hint it isn't a dedication to the Rochdale principals.
I like this idea but only as one strategy for an exit for software engineers. A majority of employees are stuck being employees and need some assistance.
That said, my personal experience with coops is that they tend to be consensus-driven and give everyone a veto. This is a problematic model when vision is required. Works well for more readily-defined things like grocery stores or running a dorm, though.
The kinds that have management representing the coop work around that problem a bit. They have someone with vision, experience, and the ability to work through disagreements. That person normally does his or her thing with others adding opinions, votes, or whatever. The critical benefit is that such a person can step in to clear out obstacles caused by a lack of consensus.
So, even with its issues, representational democracy can be better than pure democracy so long as everyone is doing his or her part. :)
http://www.forbes.com/sites/briansolomon/2013/07/24/the-wal-...
They're an employee-owned, private company in one of the most low margin and cut-throat industries around. Both their profit and effect on the competition is incredible. Also, their management to worker ratio. ;) It would be interesting to see tech companies adopt a model like this. The results could be exciting to watch and maybe lead to more job security as well given every other kind of company likes to sell out.