In this essay 15 sections
Focus is deciding which work deserves your time, people and money, then accepting that other opportunities will have to wait. It is not a lack of ambition. It is how ambition becomes a finished result instead of a collection of unfinished promises.
I like people who want to build things. I like initiative, independence and the willingness to take responsibility for an idea. None of that requires pretending every idea is worth pursuing at the same time. A capable person can create an enormous amount of activity without creating a business that works.
There is an uncomfortable distinction between having opportunities and being able to execute them. The first can make you feel successful before anything has been delivered. The second demands choices. You have to decide what the customer is actually getting, who will do the work and what you are prepared to stop doing so that promise has a chance.
The useful question is not whether you could do more. It is which work deserves to become a promise. My early building career gives me a way into that question: learning a trade, choosing when to work for myself, and finding a more useful proposal for a site. None of those decisions supplied a permanent formula. They made the next choice more concrete.
A starting point is not a destination.
In a March 2026 Press profile, I described leaving Nelson College at 16 and entering a carpentry apprenticeship. The account also records that, at 17, I formed Matthew Horncastle Builders and took on decks and fences.
Those are modest beginnings, which is precisely why they matter. A small piece of work has edges. Someone wants a result. You agree what that result is. You organise what is needed to produce it. When it is finished, the customer can examine something more substantial than your intentions.
That is a useful education in business because it makes responsibility difficult to hide. If you misunderstand the job, the misunderstanding becomes visible. If you fail to allow enough time, the clock does not care how excited you were when you agreed to the work. Your ability has to meet another person’s expectations in the real world.
I do not think a person should be embarrassed by starting with work that looks small. Small work can teach you to estimate, communicate, finish and correct yourself. An impressive title cannot do those things for you. Nor does a large address automatically make someone a serious operator.
But a starting point should not become a permanent instruction. The first thing you learn to do may not be the thing you should spend the next twenty years doing. A skill gives you options. It does not remove the need to choose between them.
The question is what the early work teaches you that can travel. You might learn that you understand a particular customer, that a certain product can be delivered reliably, or that you enjoy work other people avoid. Those are clues. They are more useful than announcing that you are ambitious and waiting for the world to decide what that means.
Earn competence before adding complexity.
Another episode in that profile concerns the move to Christchurch after work on the West Coast. I described spending a year working for a builder to improve my skills before returning to my own business and employing Blair Chappell.
I think that is an important distinction for anyone who wants independence. Wanting control over your future does not mean you have already earned every capability you need. You can be determined and still have a gap in your knowledge. Recognising the gap is a practical act, not an admission that your ambition is misplaced.
There is a temptation to use expansion to escape the discomfort of being a beginner. Add another service, enter another market or make the presentation more sophisticated. Each addition creates fresh possibilities. It can also postpone the moment when you have to discover whether the original work is good enough.
A better test is to name the capability that is missing. Not “we need to become more professional”, which can mean almost anything. Something concrete: the scope is not being understood, the work cannot be estimated consistently, or nobody can explain why customers choose one version of the offer over another.
Then choose work that develops that capability. Sometimes that means doing a smaller job properly. Sometimes it means learning from someone more experienced. Sometimes it means declining a project whose demands are beyond the people and systems currently available.
None of this requires being timid. It requires distinguishing a deliberate stretch from an unsupported promise. A stretch has a credible route through the missing knowledge. An unsupported promise relies on the hope that the knowledge will somehow arrive before it is needed.
The person buying the result should not be asked to fund that distinction unknowingly. Ambition belongs to the operator. The obligation to deliver belongs to the business.
An opportunity needs a customer, not just an enthusiastic founder.
An idea is easier to admire when it remains general. “We should move into that market” sounds sensible because it has not yet been forced to describe a customer, a price, a delivery process or a reason to choose you.
I prefer to make the idea less comfortable. Who specifically is it for? What are they trying to achieve? What are they doing instead? What would have to be true for them to leave that alternative and trust the new offer?
These are not questions that can be answered by adding an attractive image to a proposal. They require contact with the people who will use or buy the result. They also require the willingness to hear that a problem you find interesting is not a problem someone else considers important enough to act on.
Consider a hypothetical building business that is good at a clearly defined class of residential work. A new commercial opportunity appears. The founder sees a larger contract and assumes it represents progress. Yet the customer expects a different reporting process, the work requires unfamiliar coordination, and payment timing is different from the projects the team understands.
The opportunity may still be worthwhile. The larger headline does not answer the question. The team needs to understand the new promise and the resources required to make it credible. Otherwise, the existing business is quietly being used as the testing ground for a different one.
A useful customer conversation narrows the idea. It identifies the result that matters and the compromises the customer will not accept. That might make the proposal smaller. It might make it more valuable. Either is better than leaving it broad enough that everybody can imagine a different success.
Focus starts when the business stops asking whether an idea sounds exciting and starts asking whether it can deliver something that a real person wants.
A specific product changes the question.
The same Press profile describes a turning point on a Worcester Street site: instead of one three-bedroom home, I sketched three one-bedroom homes. I described finding an offer that combined quality with an accessible price and attracted buyers.
I would not turn that episode into a universal rule about the right size of a home. Different people need different homes, and different sites support different answers. The useful lesson is that a specific proposal can change the commercial question more than another general statement about growth.
The idea becomes testable. There is a type of customer. There is a layout to examine. There is a location whose advantages and limitations can be discussed. There is work to price and a finished result against which the original judgement can eventually be compared.
That level of specificity is valuable in any business. A broad ambition to provide better service is difficult to challenge. A defined promise to solve a particular problem for a particular person can be examined. People can disagree usefully because they are discussing the same thing.
The danger is mistaking the first encouraging result for a permanent formula. One successful offer may owe something to timing, location, an unusually committed team or a customer who was prepared to be flexible. Before you call it repeatable, you need to understand which parts of the result belong to the model and which belong to the circumstances.
This is where focus becomes more demanding than enthusiasm. You stay with the question long enough to learn from the details. You resist the urge to turn one promising result into five new divisions. You ask what would need to remain consistent and what should change when the context changes.
The goal is not to worship the first successful product. It is to discover the underlying capability that makes a useful result possible again.
Repeatable does not mean identical.
Repetition has a bad reputation when it is confused with indifference. People imagine a business forcing the same answer on every customer because that is convenient for the business. That is a poor version of standardisation, and customers are right to resist it.
The useful version is different. It makes the reliable parts of delivery easier to repeat so that attention remains available for the decisions that genuinely depend on context.
A builder should not need a new philosophy of communication for every job. A customer should be able to understand who is responsible, what has been agreed and how changes are handled. Those basics can be consistent even when the site, design and people differ.
Nor should a business confuse consistency with refusing to learn. If a detail keeps creating confusion, repeating it faithfully is not discipline. It is evidence that the standard needs attention. A good system carries the reason for a decision as well as the decision itself.
In a hypothetical project review, the team might discover that two customers received different explanations of the same inclusion. The immediate job is to resolve the individual misunderstanding. The wider job is to identify the source of the inconsistency and make the next explanation clear. Otherwise, the organisation is paying repeatedly to learn the same lesson.
I would judge repeatability by whether an ordinary capable team can produce the intended result without permanent rescue work. That is a harder test than asking whether a particularly determined founder can force one job over the line.
It also respects the people doing the work. A clear process should reduce avoidable uncertainty, not remove their judgement. If every situation is treated as an exception, nobody has a dependable platform. If no situation is allowed to be an exception, nobody is allowed to think.
The balance is to be consistent about the promise and intelligent about the circumstances in which it must be delivered.
The cost of a new idea includes what you can no longer do.
Money is an obvious constraint. Attention is easier to disguise because it does not arrive as a separate invoice. That does not make it unlimited.
A new venture may require decisions from the same people who are already responsible for delivering the existing work. It may need the founder’s time, a trusted manager’s judgement, introductions from a partner or the goodwill of a supplier. None of those resources can be allocated twice simply because the spreadsheet lists the businesses in different columns.
That is why I think every serious proposal should say what will stop or reduce if it goes ahead. If the answer is “nothing”, the proposal may be assuming spare capacity that has not actually been demonstrated.
This is not an argument that busy people should never take on more. It is an argument for being honest about the exchange. Some existing activity may be low value and deserve to disappear. Some work may be delegated successfully. Some capacity may be created by improving a process. Each is a real explanation. “We will work harder” is not automatically one.
Imagine a manager who currently spends two days a week resolving unfinished details across projects. A new service business is proposed on the assumption that this manager can run it. Before accepting that assumption, find out whether the two days of existing work can genuinely be removed, reassigned or prevented. A new title will not make those details cease to exist.
The exchange should also be visible to the people who carry it. Otherwise, a founder experiences the excitement of a new opportunity while the team experiences a quiet increase in promises and a decline in available support.
Choosing what not to do is one way to make ambition fairer. It prevents the cost of the founder’s enthusiasm from being hidden inside everybody else’s week.
Diversification is not the opposite of focus.
The strongest objection to a narrow business is obvious: concentration creates exposure. A company dependent on one product, one customer or one market can be vulnerable when circumstances change. Having more than one useful source of work can be sensible.
I agree with that objection. I do not agree that it settles which new activity to pursue.
Diversification describes a broader set of activities or exposures. It does not guarantee that those activities are understood, well run or genuinely different from one another. A collection of businesses can share the same customers, the same market conditions and the same small group of decision-makers. There may be more names without much more independence.
Equally, a related service can make the overall offer more useful. Customers do not necessarily divide their needs according to the legal structure of the businesses serving them. A home has to be built, bought, occupied and looked after. There can be a sensible reason for several distinct capabilities to exist around that journey.
The question is whether each capability earns its place. Does it solve a real customer problem? Is its responsibility clear? Can its performance be understood on its own terms? Is the group gaining something more durable than the ability to cross-promote a longer list of names?
My ventures directory includes more than one business because focus does not mean everybody must own one company or sell one thing. It means the purpose of each activity should be explainable, and the resources committed to it should be deliberate.
A focused group can contain several businesses. An unfocused business can exist inside a single company. Structure matters, but it cannot substitute for judgement about what the organisation is capable of promising and delivering.
The useful contrast is not small versus large. It is coherent versus accidental.
Keep an opportunity list, not a promise list.
Rejecting an idea for now does not require pretending it is a bad idea. Timing and readiness matter. A proposal can be attractive and still be wrong for the business at its present stage.
I would give interesting opportunities somewhere to live without allowing them to become informal commitments. Otherwise, every conversation creates another half-project that somebody assumes has been approved.
A simple opportunity note can be more useful than a large speculative plan. Write down the customer, the problem, the proposed result, the evidence currently available and the largest unresolved question. Then identify what would justify spending more time on it.
The distinction between exploration and commitment needs to be explicit. Speaking to potential customers is not the same as promising a launch. Obtaining an estimate is not the same as approving a purchase. Asking a colleague to investigate something should not silently turn into asking them to build it.
For a hypothetical new service, the next useful step might be five substantive customer conversations rather than a logo and a website. Those conversations should investigate what customers already do, where it fails and what they consider a worthwhile improvement. They should not be an exercise in persuading friendly people to compliment the idea.
At the end, record what changed. If the evidence did not resolve the main uncertainty, acknowledge that. An investigation is not successful merely because it produced a document. It succeeds when the next decision is better informed.
Keep the list short enough to review honestly. An enormous register of opportunities can become another way to avoid choosing. Its purpose is to preserve good thinking while protecting the organisation from carrying commitments that have never been made deliberately.
A possibility can wait. A promise has a customer at the other end.
Define the test before you see the result.
People are inventive when they want to protect an idea. If the original target is missed, they can discover a different measure that makes the experiment sound successful. There is nearly always some encouraging detail available if you look hard enough.
That is why a small test needs a clear question before it begins. What uncertainty are you trying to reduce? What would count as useful evidence? What result would justify stopping rather than increasing the commitment?
Consider a hypothetical service trial. The team wants to know whether customers will choose a defined offer at a sustainable price and whether it can be delivered through the existing operating model. Expressions of interest alone cannot answer both questions. Nor can one successful delivery that required unrecorded help from half the company.
The review should separate customer demand from delivery capability. A product may be wanted but difficult to provide consistently. A process may be efficient but produce something customers do not value. Each failure teaches something different and calls for a different response.
It is also worth recording the exceptions. Which parts worked only because a particular person intervened? Which costs were temporarily absorbed elsewhere? Which promises were softened because the customer knew it was a trial? Those conditions do not make the test worthless, but they should travel with the result.
I do not expect experiments to be perfectly clean. Real businesses have to learn while operating. I do expect the conclusion to reflect what the experiment actually showed.
A disciplined test can produce a disappointing answer and still be a good use of time. Discovering a weakness before making a large commitment is useful. The expensive version is conducting a test while refusing to allow any outcome other than the one you wanted.
Measure the work, not the excitement around it.
Activity can look convincing from a distance. Meetings are happening. People are interested. A proposal has been circulated. The branding is finished. A launch date has been discussed. These things may be necessary, but they are not interchangeable with delivery.
I would start a focused review with the promises made to customers and the work required to meet them. What is complete? What is waiting? What has changed? Who owns the next action? These are ordinary questions, which is part of their value. They make it harder to replace a stalled result with an energetic explanation.
Then look at the quality of the result. Did the customer receive what was agreed? Was the work completed in a way that the business can repeat? What remains unresolved after the apparent finish line? A job that has been invoiced may still contain obligations that someone will have to fulfil.
The measures should fit the business rather than imitate a fashionable dashboard. An early offer may need evidence of genuine demand. A repeatable service may need information about reliability, rework and the time needed to deliver. A mature operation may need to understand where performance is slipping despite apparently stable totals.
One number rarely tells the whole story. More work can coexist with more mistakes. Faster delivery can coexist with problems that have simply been pushed into the customer’s future. A growing customer list can coexist with a promise that the organisation cannot support.
Ask what a measure leaves out and who experiences that omission. That is not an excuse to avoid measurement. It is how measurement becomes useful rather than decorative.
The standard should be intelligible to the people doing the work. If the team cannot explain why a number matters to the customer or to the business’s ability to keep its promises, it is worth asking why that number is receiving so much attention.
A new venture needs an owner, not a spare title.
A proposal often sounds complete when it includes the name of the person who will run it. That is only the beginning of the responsibility question.
What can that person decide? Which resources are actually available? Which parts of the promise depend on another team? What happens when the new work conflicts with an existing obligation? Who decides between them, and on what basis?
Without those answers, the named owner can become a messenger. They carry responsibility for the outcome but must negotiate repeatedly for the means to produce it. The founder then becomes the route through every disagreement, and the new venture consumes more attention than the proposal admitted.
I would rather see a smaller mandate with real authority than a grand title with no practical room to act. The owner should understand the boundary of the assignment, the decisions reserved for others and the evidence that will be reviewed.
That does not mean removing oversight. Independence is more credible when expectations are clear. The person running the work should be able to surface a problem early without having to defend the continued existence of their role in every conversation.
There should also be an honest account of their previous responsibilities. If they are taking on new work, which existing commitments move? Who receives them? How will the handover be checked? “They will manage both” may be possible, but it needs more support than confidence in their work ethic.
People deserve clarity about the job they have actually accepted. A business should not rely on capable staff absorbing every unresolved choice through personal effort.
The founder’s responsibility is not only to attract good people. It is to create a situation in which their judgement can produce a result.
Stopping can be a responsible decision.
It is easy to praise persistence in the abstract. The harder question is what you are persisting with. A worthwhile purpose may deserve commitment even when a particular product, process or market does not.
I do not think integrity requires defending every past decision indefinitely. It requires being honest about what was promised, what has happened and what obligations remain. Sometimes the responsible choice is to change direction. Sometimes it is to stop taking new work while existing promises are completed.
Stopping badly is destructive. Customers are left uncertain, staff receive vague explanations and suppliers have to discover the change for themselves. That is not focus. It is passing the cost of a decision to people who did not make it.
A deliberate wind-down is a different proposition. It identifies outstanding commitments, allocates responsibility for them and communicates what people need to know. The details will depend on the business and may require professional advice. The operating principle is simple: ending an activity does not erase the promises already attached to it.
There is also a distinction between closing something and allowing it to drift. A drifting project can absorb small amounts of attention for years because nobody wants the discomfort of an explicit decision. The cost is distributed and therefore easy to underestimate.
I would ask whether the work has a credible next step, a responsible owner and a reason to receive resources now. If it has none of those, it should not survive merely because it once appeared in a strategy document.
The ability to stop is part of the freedom to build. Without it, every old idea has a permanent claim on the future, and the business becomes less capable of choosing the work that matters next.
Do not confuse confidence with capacity.
Confidence helps people begin. It can make an uncertain opportunity worth investigating and give a team the energy to solve a difficult problem. I value it. I also think it needs something solid to stand on.
Capacity is not a feeling. It is the combination of people, skills, time, systems and resources available to deliver a promise. A confident founder cannot make an overloaded manager available in two places at once.
A useful review separates what exists from what is expected to exist. A person already in the role is different from a hoped-for hire. A process that has worked repeatedly is different from one described in a plan. A confirmed commitment from a partner is different from an encouraging conversation.
These distinctions can sound pedantic when everyone is excited. They become important when several assumptions fail to arrive on the same day. The purpose is not to remove uncertainty, which would remove much of business. It is to see where the uncertainty sits and decide whether the organisation can carry it.
I would be especially careful where a new proposal depends on uninterrupted success elsewhere. If the existing work must run perfectly for the new work to survive, the organisation may have less room than the headline opportunity suggests.
That is an operating observation, not a funding recommendation. The appropriate capital structure, contractual obligations and financial decisions depend on the circumstances and the relevant professional advice. No general essay can determine those for a particular business.
The practical point is to make the dependencies visible. Confidence is useful when it motivates the work needed to resolve them. It becomes expensive when it is used as a reason not to examine them.
A focus review you can actually use.
Here is the review I would use to make a proposal concrete. It is deliberately short enough to discuss around a table without a presentation becoming the main event.
First, write the promise in ordinary language. Name the customer and the result. If the sentence needs several vague words such as innovative, leading or comprehensive to sound worthwhile, keep working on it. The customer should be able to recognise the problem without being taught your internal language.
Second, identify the evidence. Separate what has been observed from what is assumed. A real purchase, a completed delivery and a customer interview are different kinds of evidence. Record what each tells you and what it does not.
Third, name the owner and the constraints. Who can make the daily decisions? What time and resources are available? Which other teams are needed? State the existing work that will stop, reduce or move so the new promise is not financed through invisible overload.
Fourth, define the smallest meaningful test. It should answer an important uncertainty, not simply make the idea look active. Agree how the result will be reviewed and which outcomes would justify expansion, revision or stopping.
Fifth, describe the obligations that follow a decision. If the test becomes a permanent offer, what must be reliable? If it stops, what must still be completed? Customers and staff should not discover that the organisation treated a promise as an experiment only after something goes wrong.
Finally, set a review point and keep the original reasoning available. Not to punish someone for being wrong, but to learn whether the judgement improved. A decision record should help the business become more capable, not give people a new reason to hide uncertainty.
The value is in the conversation and the choices it forces. A completed checklist is not proof that an opportunity is good. It is a way to expose the assumptions that a good decision needs to confront.
Give ambition an address.
I do not want ambition reduced to a cautious version of whatever already exists. New companies, new products and better ways of building need people prepared to try something. A country that discourages that instinct will not become more productive by congratulating itself on its restraint.
But the alternative to timidity is not permanent expansion in every direction. It is purposeful commitment. Choose something worth doing. Understand enough about the customer and the work to make a credible promise. Then give that promise the attention it deserves.
Focus can make a business look less impressive on paper for a while. There may be fewer launches, fewer announcements and fewer ideas with names. What matters is whether the work that remains becomes more useful, more dependable and easier to stand behind.
I would rather have a clear account of what has been finished than an elaborate account of what might happen if every opportunity receives resources at once. Finished work gives the next decision a stronger foundation. Unfinished promises compete with it.
Starting small is not the same as thinking small. Learning a trade, completing a modest job and finding a product that people choose can each become the beginning of something larger. The size of the beginning is not the limit. The quality of the learning matters more.
The discipline is to keep choosing. Keep the useful capability. Improve the promise. Let go of work that no longer earns its place. Ambition becomes real when it has an address, an owner and a result that another person can use.