For routine matters with clear authorization, the authorized person can decide within that scope. If a decision needs joint consent, an applicable rule requires a pause after an objection, or authority is unclear, pause the disputed action. Record who will decide what happens next and when. Calling yourselves partners tells you little about who has the final say. Check the legal structure and governing documents before weighing the options.
In twenty minutes, you can turn “Should we launch tonight?” into a set of separate decisions. For each one, write down who can approve it, who can stop it, and how you’ll honor any promises you’ve already made to customers if it stops.
Step 1. Check the documents and identify who can decide today
| How the business is organized | What to check first | What to do today |
|---|---|---|
| A partnership contract governed by China’s Civil Code | Check the agreement for provisions on decision-making and authority to act. Under Article 970, decisions about partnership affairs require unanimous consent unless otherwise agreed. Where partners carry out affairs separately, the other partners must suspend the matter if a partner responsible for carrying out partnership affairs objects | Pause the disputed matter until you have the required consent |
| An enterprise partnership governed by China’s Partnership Enterprise Law | Check the partnership agreement and the statutory rules for the specific matter. Under Article 29, when partners handle affairs separately, the matter must be suspended after an objection by a partner responsible for carrying out partnership affairs. Under Article 30, voting follows the partnership agreement. Where the agreement is silent or unclear, the usual default is one vote per partner and approval by more than half of all partners, subject to any other statutory rule | With two partners and one vote each, one vote falls short of a majority. Matters listed in Article 31 require unanimous consent unless the partnership agreement provides otherwise |
| A limited liability company | Check the articles of association, valid resolutions, and written authorizations. Article 65 of China’s Company Law defaults to voting rights in proportion to capital contributions unless the articles provide otherwise. Article 66 requires resolutions at shareholders’ meetings to pass with more than half of the voting rights. Amending the articles, increasing or reducing registered capital, merging, dividing, dissolving, or changing the company’s legal form requires at least two-thirds of the voting rights | Separate delegated operating decisions from matters that require a formal resolution. Check who can operate the controls and who has authority to approve the action |
Chinese legal-practice articles commonly frame these disputes around 50/50 ownership, deadlocks, and exit arrangements. This example addresses a narrower operational dispute: can a trial happen today? If the deadlock already involves a partner’s exit, the company seal, or signing a contract, preserve the relevant documents and follow the applicable formal process for that dispute. Civil Code, Article 970 · Company Law, Articles 65 and 66 · Partnership Enterprise Law, Articles 29–31 · Original legal-practice article on business partnerships
Step 2. Break the launch dispute into three separate questions
A shop trying out a new set menu can limit it to one shift and agree on who can pull the menu. A trading team testing a new supplier can set the order quantity, acceptance criteria, and authority to halt purchases in advance. Here’s what that agreement can look like for a redesigned booking page.
Fictional example. Lin Yue handles operations. She’s booked five customers to try the redesigned booking page on Friday at 16:00. Chen Dong handles engineering. The new page opens, but he hasn’t checked whether unfinished bookings can return to the old flow when he turns off the new page. If the full switch fails, it could affect real bookings. At 15:30, they break the dispute into three questions.
- What must customers get today? Lin Yue checks the invitation email. It promised a chance to try the page and give feedback. It made no promise of a switch for all customers.
- Which trial setup can avoid writing any live records? Chen Dong proposes an isolated demo entry point, demo accounts only, and disabled live booking submissions and notifications. Limiting the demo to five customers cannot remove the risk of live writes if the demo and production bookings still use the same write path.
- Who approves moving from a small demo to a full rollout? Their existing written agreement lets operations coordinate demo appointments while requiring both partners to approve a switch of the default live page. Before changing the scope for the day, they agree on the demo’s boundaries. Lin Yue handles communications and Chen Dong verifies the setup.
DACI separates approvers from contributors. RAPID distinguishes the decision-maker from the people who carry out the decision. For decisions within existing authority, this example boils those roles down to who approves, who acts, and who can stop the work. The demo can proceed once they’ve checked isolation, confirmed they can shut it down, and verified recovery. Atlassian DACI · Bain RAPID · Microsoft guidance on safe deployments
Step 3. Turn “let’s try it” into a decision people can execute
| Record item | Agreement at 15:30 on Friday |
|---|---|
| Approved scope | Five customers who opt in can try filling in the form with demo accounts. The trial creates no live bookings. The old page remains the default in production |
| Conditions to start | Chen Dong submits a test form to check that no live booking or notification results. He then verifies that both he and his backup can shut down the demo entry point. Lin Yue checks the invitation wording |
| Stop triggers | A live record is written or a notification is sent, a participant cannot exit, or the team finds it cannot shut down the demo as agreed |
| Who acts | Chen Dong shuts down the demo and tells Lin Yue. If he is unavailable, an authorized on-call engineer who has demonstrated the ability to shut it down takes over |
| Checks after shutdown | Chen Dong checks the old entry point and confirms customers can still submit normal bookings. He and Lin Yue then check whether the demo left any live bookings or sent any notifications. If it did, Chen Dong preserves the original records, logs the record IDs, scope, and discovery time, and asks the on-duty operations supervisor authorized to handle bookings in this example to confirm whether a correction is needed and when it can be completed under the existing process. Lin Yue uses the record to tell affected customers which bookings still stand, what they need to do, and when she’ll follow up. |
| Customer fallback | If the isolation checks are still incomplete by 15:55, Lin Yue switches to a static demo and collects feedback on the spot. Live bookings continue through the old entry point |
| Review and default action | At 11:00 on Monday, review the isolation record, rollback test, and trial feedback. Even if rollback worked, leave the default page in place if the two partners still disagree. Chen Dong sets the next checkpoint and Lin Yue tells customers what happens next |
Counterexample. The partners agree to “try it with two customers” without checking whether the trial and live page share data. If even one submission could create a live booking, the proposed trial is still missing a precondition. They can show a static prototype at the scheduled time or reschedule. The reverse can happen too: rollback works, the demo runs without incident, and one partner still thinks a wider rollout could create a support workload no one has accounted for. Write the objection as something you can verify, such as “Who handles feedback on new bookings over the weekend, and can they take over by the agreed time?” Put it on the agenda for the next review.
You can copy this line into your meeting notes:
Decision ___ / Approver ___ / Allowed scope ___ / Prohibited scope ___ / Checks before starting ___ / If ___ happens, ___ stops the work, with ___ as backup / ___ verifies live records and hands them to ___ for processing / ___ updates customers at ___ / Review at ___ using ___ / Default if no agreement by then ___.
If losses have already occurred or an external deadline is near, escalate under the existing emergency authorizations and formal procedures instead of defaulting to an indefinite delay. To reflect on how you handled the conversation, use the EQ-60 Emotional Intelligence Self-Assessment to organize observations about your awareness and interactions. It does not assess your partners’ authority, ability, or trustworthiness. You can also see how to check an objection raised in a meeting and how to make feedback clear.
Frequently asked questions
If two shareholders each hold 50%, who gets to decide?
Check the matter at issue, the rules for the entity type, and the wording of the articles, resolutions, and authorizations. Ownership percentages alone do not tell you whether one shareholder can approve this action independently.
If one partner opposes a full rollout, can the other start a small trial?
First confirm that the trial genuinely counts as a separate matter, falls within the applicable authority, and meets the agreed isolation and stop conditions. If an applicable objection rule requires this matter to pause, suspend it and follow the formal process.
What goes in the decision record if you still disagree after the meeting?
Record what remains open, the current default action, what evidence you still need, who is responsible, when you’ll review it again, and what you’ll tell customers. The default action also needs to be within existing authority.
References reviewed (editorial appendix)
| Original page | How this article uses it | What this article adds |
|---|---|---|
| Chinese legal practice on business partnerships | Identifies 50/50 ownership and deadlock concerns for readers in China. The rules come from the statutory text | Tests authority in both routine launch operations and formal governance decisions |
| DACI | Organizes decisions by role | Specifies when to pause and how to obtain agreement if authority is unclear |
| RAPID | Distinguishes contributing, deciding, and executing | Adds a backup for shutdown, a handoff for customer communications, and a review time |
| Microsoft guidance on safe deployments | Uses checks, observation, and recovery to constrain a gradual rollout | Offers a fallback that still lets the team record customer feedback if isolation fails |


