What did the founders actually put to a vote?
At ten past nine on a Sunday morning, Lia told the engineering lead to leave two names off the sprint plan until she could give him an answer. A museum festival in Israel was preparing to stage a play in a hall with unreliable internet. Lia and Oren’s company supplied the software that put English captions above the stage. The museum wanted the captions to keep running if the connection dropped. Its producer needed to know by Thursday whether to book a different hall. She had good reason to ask for an answer. Every switch of venue meant another visit with the production crew.
On the previous afternoon’s call, Lia had shared the sprint calendar on screen. “I’m asking us to move Noa and Gil off their scheduled work for the next two weeks, build an offline version for this hall and tell the museum on Sunday that we’re going ahead.” She was willing to put two customers’ smaller requests back a fortnight to keep the festival contract. Oren had been in the hall during rehearsal. He had watched a technician restart the caption computer halfway through a scene. Keeping a copy of the captions on the machine sounded promising to him. Promising reliable operation before anyone had tried a restart sounded like a different proposition.
“I vote yes,” Lia had said. Oren had answered, “On moving them for two weeks and giving the museum a commitment now, I vote no.” Yael, the finance manager, had said, “I’m here for the cost figures. I’m staying out of the vote.” Amir, whom Lia remembered as the third director, had been invited and had not joined. The calendar invitation called it a festival delivery meeting. Oren had ended the call believing they had declined the museum’s request. Lia had ended it believing the decision was still open. By Sunday, staff had heard both accounts.
If you are in Lia’s position, the most useful sentence you can write that morning is the one both founders can recognize as the question they answered. Here it covered two engineers, two weeks away from scheduled work and a commitment to the museum before an offline build had been tested. A vote against that package says little about how Oren would vote on a trial in the hall. Equally, Lia’s willingness to release the engineers for two weeks does not tell the engineering lead he can start with half a day.
Lia called Oren before she answered the team. “Can we agree nobody came off the sprint during that call, and neither of us told the producer she could count on offline captions?” Oren said yes to both. He checked his sent messages while they spoke. His last note to the producer had promised an update about the room, not a feature. They could now give the engineering lead one accurate fact. The call had produced no agreed instruction to reassign Noa and Gil. Whether it had also produced a formal company decision was a separate question.
Was it a directors’ meeting?
Lia opened the invitation while Oren pulled up the notes he had typed during the call. The invitation included the engineering lead for the first fifteen minutes and Yael for the budget discussion. Amir’s name appeared among the guests. The description said “festival delivery and staffing.” There was no motion attached. Lia remembered saying they needed a decision from the board. Oren remembered hearing that towards the end, after the engineering lead had left. Neither could recall anyone asking the people present whether they understood that they were now meeting as directors.
The title of the invitation could not settle the matter. Directors sometimes discuss a decision at a meeting whose calendar title says little about its purpose. Managers can also take a show of hands to find out whether their colleagues support a plan. The words “I vote yes” establish what Lia said. They do not establish the capacity in which she said it. The founders needed the invitation as sent, any later message explaining the purpose, the applicable meeting procedure and a reliable account of who was present when Lia put the question. A recollection that everyone knew the festival was urgent would answer none of those points.
Yael helped clear up one ambiguity. Oren’s notes said “Yael abstained.” When he read that back to her, she explained that she had never understood herself to have a vote. She had attended to explain the cost of rescheduling customer work. She could confirm that Lia said yes and Oren said no, and that the engineering lead had left before either spoke. That was useful evidence from someone who heard the exchange. It gave the founders no basis to count a third ballot or to describe Yael as a director who formally abstained. They kept the original note and recorded her explanation separately.
Amir’s absence needed the same care. His name on the invitation showed that a message had been addressed to him. He confirmed later that he had been at a performance and had not taken part by phone, sent a vote or asked anyone to vote for him. He also remembered signing something about his board role during the previous financing. He could not remember whether it concerned his own appointment or the right to nominate another person. Guessing how he would have voted would add nothing. Even the question of whether his absence mattered for quorum depended on documents the founders had yet to locate.
By lunchtime, Lia and Oren had a short account they could both stand behind. Lia put the combined proposal, she supported it, Oren opposed it, Yael declined to participate in a vote and Amir was absent. They had not established that the call was a directors’ meeting or that a formal resolution had passed or failed. They left those conclusions open. Oren’s working notes remained his working notes. There was no reason to turn them into signed board minutes that neither founder could defend.
First establish whether this was a vote of the board. Section 107 of Israel’s Companies Law concerns board decisions and ties. Its default is an ordinary majority with an additional vote for the board chair in a tie, subject to different provisions in the articles. This does not establish that the founder who chaired the conversation had a deciding vote. Check who was appointed to which role, any special rules, how the meeting was convened and whether the issue fell within that body’s authority. A meeting of shareholders raises a different voting question.
Which company records answer this particular question?
Lia and Oren each owned half the shares in their Israeli company. Both were used to being asked for a decision whenever the other was unavailable. This time their disagreement made a distinction visible that ordinary working days had concealed. The shareholder register could help establish their holdings. It could not tell Noa whose instruction to follow on Sunday morning. Nor could it tell the museum producer whose email would amount to a company commitment. Each question called for a record that addressed the particular act.
Lia asked the person who kept the company records for the articles in force when the call took place, together with the amendments and decisions needed to identify that version. Oren found two files with almost identical names. One contained a provision about the chair having a casting vote. The other did not. The later file on his laptop was a marked copy circulated during financing discussions. Its modification date showed when someone had saved it. It did not show that the company had adopted it. They asked for the adoption record and retained both copies with their original filenames.
The scope of the provision mattered as much as the version. If they found a casting vote in the applicable articles, they would still need to read which body it concerned, who was chair, when the provision applied and whether this meeting met those conditions. If the applicable text required a particular quorum, they would need to check attendance at the point of decision against that requirement. A director’s presence during the cost discussion would not prove that the director was still there for the vote. Until the appointment records, agreed procedures and meeting facts supported an answer, “we haven’t established the result” was the accurate entry.
Separately, they looked for the authorization under which engineering time was normally assigned. An earlier board decision had been mentioned in emails about staffing. Lia wanted the decision itself, including its attachments and any later change. She usually set product priorities, and Oren usually managed customer delivery. Moving two engineers for a fortnight could involve both jobs, especially if the move displaced work already promised elsewhere. The question was precise enough to put to someone familiar with the company records. Did the current delegation cover a change of that size, for that purpose, with those effects on existing work?
The signed museum agreement raised another distinction. Lia had introduced the company to the museum. Oren had sent every rehearsal schedule. Yael could see from the bank mandate who was authorized to make payments and under what conditions. None of those facts by itself identified who could commit the company to deliver a new software feature. Lia pulled the signed agreement, its schedules and the subsequent correspondence about the hall. The founders wanted to know what delivery had already been agreed, who could send an ordinary update and what authority was needed to approve a change. Permission to discuss a rehearsal time could be sufficient for that conversation and still leave the offline commitment unresolved.
What should happen on Sunday morning?
At eleven the engineering lead showed Lia the version of the sprint plan the team had been working from on Friday. Noa was due to fix a timing error that put one character’s captions over another’s lines. Gil was due to help an existing theatre install the release it had rehearsed with. Both jobs had named customers and agreed handoffs. The lead could verify those assignments from the work queue and the customer schedule. He also confirmed that he had made no offline assignment since the call. That gave Lia and Oren a factual answer for the engineers. Their existing assignments still stood.
The lead then showed them a message from Gil. “Should I at least copy the captions onto a spare machine and see what happens when the cable comes out?” It was an excellent technical question. It was also a request to spend project time on the very work the founders were discussing. A small test might later give them a better basis for deciding. For now it was a proposal, and it needed approval from whoever had authority for that use of time and equipment. Lia thanked Gil for identifying a test worth considering. He could finish the theatre installation without trying to interpret her thanks as a quiet instruction to start.
Yael had a different concern. A caption operator was due to be paid for Friday’s rehearsal, and the regular payroll run was approaching. She could verify the rehearsal invoice against the existing booking and check the payroll schedule in the usual way. The current bank mandate and payment workflow would identify the signatories needed for each authorized payment. There was no operational reason to bring the offline disagreement into either transaction. Yael needed the normal approvals to move on time. She had no need for a verdict on which founder had been right on the call.
The museum producer still deserved an answer to the question she had actually asked that morning. Could she release the backup hall? Oren found the email naming him as the operational contact for scheduling. Lia and Oren agreed on the facts he could convey within that role. Offline operation in the proposed hall had not been confirmed. The existing rehearsal remained on the calendar. The producer replied that she could hold the backup hall until noon on Thursday and asked him to let her know sooner if the position changed. Oren entered that deadline in the delivery calendar. The museum could now make its own plans with an accurate understanding of what the company had confirmed.
Just before lunch, Lia called the engineering lead back. She could tell him what he had needed to know at nine. Noa and Gil had work to do that was already authorized, the museum had heard from its scheduling contact, and nobody had approved an offline test. The open question still had a definite shape. Should the company release those two people for two weeks and commit to offline captions for this festival? Lia’s yes and Oren’s no were on record, along with what Yael and Amir had actually done. The status of the meeting and the authority to decide remained open where the records were inconclusive. That was enough to get through Sunday without making staff or the museum settle the founders’ disagreement for them.
Put the unfinished decision back on the table
Start with the motion that stalled. Lia moved that the company assign two engineers to build a custom offline mode for the museum festival. She voted for it and Oren voted against it. Before either founder speaks to the engineers, they should check the account of the meeting against what actually happened. Did the motion include a promise to deliver by opening night, or did Lia ask only for engineering time? If a delivery promise came up in discussion but never made it into the motion, the distinction matters. Oren may have voted against committing two people without knowing how long the work would take. Lia may have heard his vote as a refusal to serve the museum at all.
Ask each founder to finish the sentence “I understood that a yes vote would let us do this tomorrow.” Lia might say she expected an engineer to investigate how captions would behave during a network outage. Oren might say he expected the museum to be told that offline captions were on their way. Write down both answers. Keep the original account of the vote accurate, including any difference of recollection. A narrower proposal can go to a fresh decision. It should never be written back into the minutes as something the directors already agreed to.
Separate the practical roles as well. Lia might ordinarily schedule engineers while Oren handles museum correspondence. An authorization to sign at the bank answers a different question from either one. The person who can release a payment may have no authority to approve the underlying work. The person who can answer a museum email may have no authority to promise a feature. Give the next meeting one concrete purpose. By the end, the founders want a decision from the right people about a defined amount of work, and a clear answer about what the museum contact may say.
Find the deadline that changes the choice
Suppose the museum asks for an answer by Thursday. Lia hears a deadline for securing the festival contract. Oren hears a producer who would prefer to finish the weekly schedule. The person authorized to speak with the museum can resolve much of that difference without offering anything. A useful question is “What do you need to decide on Thursday, and what will you do if offline captions are still unconfirmed?” The producer might need to book a caption operator who can run the existing system from a room with a wired connection. Once that room goes to another production, a fallback disappears. That makes Thursday consequential even if the company has another month to decide whether to develop the feature.
Ask what answer the producer actually needs. “We need to know whether to retain the wired room” is quite different from “We need offline captions running in the festival hall on Thursday.” The first allows the museum to make its booking while the company considers a limited test. The second may leave no room for a test that finishes on Friday. Check the existing festival commitments before describing either answer to the museum. A producer’s willingness to wait for news does not by itself settle what the company has already undertaken to deliver.
Apply the same scrutiny inside the company. If Oren says the engineers cannot spare a day, ask which scheduled work would move and who is relying on it. He may identify a caption timing fix due for the next theatre performance. Lia can then ask whether four hours on Wednesday would delay that fix or whether the real conflict begins when a second engineer joins on Friday. If Lia wants a demonstration because the festival team is meeting on Friday, ask what that team could decide from a demonstration. An internal preference for showing progress should carry less weight than the museum losing its only workable fallback.
Reversibility also depends on who has started relying on the choice. An engineer can discard an experimental build. The hours spent on it are gone, and the museum cannot necessarily get its wired room back once it releases the booking. Consider the smallest useful answer the company can give now. If it falls within the contact’s authority and accurately reflects the current service, that might be “Offline mode is unconfirmed for the festival. Please plan on the wired setup.” That gives the producer something definite to act on while keeping the founders’ unfinished decision inside the company.
Ask what evidence could change a vote
Before costing a pilot, give each founder the chance to name a result that would change a specific decision. Ask Lia, “What result would make you stop pursuing offline mode for this festival?” She might say that if captions lose their place after the operator jumps back a scene, she would support the wired setup. Ask Oren, “If the cues stay in sync after that jump, what would you vote for?” He might support a supervised rehearsal but still oppose a delivery promise. Those answers define a useful experiment. No one has to pretend that a successful rehearsal would settle the larger question.
Be precise about a negative result. If the captions drift, Lia wants to know whether the operator can recover before the next line appears. Oren wants to know whether recovery requires an engineer beside the operator. They can agree to observe both. They can also agree that an interrupted test or a missing measurement leaves the question open. Otherwise, Lia might count a run as a pass because the final caption appeared, while Oren counts it as a failure because somebody corrected the timing by hand. Decide in advance whether that intervention is part of the proposed service.
Some disagreements call for independent advice. Suppose Lia thinks the existing museum commitment already covers offline operation and Oren reads it differently. A flawless demonstration cannot answer that question. They can identify the disputed wording and the relevant correspondence, then seek advice from an independent Israeli commercial lawyer through an authorized engagement. A separate question about whether a manager can approve experimental work can likewise be put to an adviser with the relevant corporate records. Ask for an answer to the point that affects the decision. Keep the engineering assessment separate so a technical opinion does not end up standing in for advice about authority.
There may also be a difference neither evidence nor advice will remove. Oren might accept that offline mode is feasible and still prefer to spend the available time fixing captions for existing theatre customers. Ask him directly whether any successful test would change his vote on festival delivery. If the answer is no, take him at his word. The founders can still decide whether a small test has value for a later production. They should give the engineers that honest purpose, especially if the museum needs a final answer before the test can finish.
Compare two pilots before asking for approval
Consider two hypothetical pilots for the same festival decision. The dates, budgets and pass conditions below are planning assumptions. Neither pilot may begin until the person or body with the necessary authority approves its scope, staff time and spending under the company’s actual arrangements. Check that staff can be assigned within that authority and that any outside contact has its own approval. When comparing costs, use the same basis for both options. Here the shekel caps cover additional expenditure, while hours of existing employees are shown separately so that taking them off other work remains visible.
The first pilot is an internal bench test. On 10 March, one engineer would spend up to eight hours on a disposable build. A caption operator would spend up to two hours running a fictional ten minute scene on a company laptop. The proposed spending cap is NIS 600 for equipment rental if needed. The operator would load sixty invented cues, disconnect the laptop from the network and jump back one scene twice. The question is whether the next cue appears within one second of the operator’s command after each jump, without an engineer intervening. No museum script, customer account or festival device is needed. The museum receives no demonstration and has no reason to change its booking.
Stop the bench test when either hour allowance or the cash cap is reached, or sooner if the test would require a change to a live customer system. At the review on 11 March, the engineer would report the delay after each jump, any missing cue and whether the operator needed help. Two successful recoveries would give Oren a reason to consider a rehearsal. They would tell Lia little about the festival hall itself. If the first jump fails and the engineer spends the remaining hours diagnosing it, record the second jump as untested. The founders can then decide whether the diagnosis alone is worth another request.
The second pilot is a closed rehearsal in an empty museum room on 12 March. Two engineers would have up to six hours each, and the company’s caption operator would have three hours. The proposed cap is NIS 2,400 in additional spending for transport and equipment hire. The authorized museum contact would first need the museum’s agreement to a forty minute room booking and a clear understanding that there will be no audience, installation or promise of opening night service. The operator would run a twenty minute fictional scene twice on an isolated laptop, once from the beginning and once after a simulated interruption. The company would use invented cues and keep the museum’s normal network and visitor systems outside the exercise.
Stop the rehearsal if the room becomes needed for festival work, anyone requests access to a live system, or the time or spending allowance would be exceeded. At the review on 13 March, the founders would hear whether the operator resumed on the correct cue within five seconds of the restart command and completed the scene without engineering assistance. This pilot costs more staff time and asks something of the museum. It answers a question the bench test leaves open, namely whether the operator can recover in the room under rehearsal conditions. If Thursday’s booking decision comes first, tell the museum to retain its fallback. Even a successful rehearsal goes back for a separate decision about any further work or customer commitment.
Give the decision a clear ending
At the follow up meeting, put the two requests into ordinary speech. Lia could say, “I’m asking for eight engineering hours and two operator hours for the internal test. If we get both recoveries, I’ll bring the results back before asking anyone to approach the museum about a rehearsal.” Oren can then answer the request in front of him. “I can support that if the timing fix goes out first. I want the engineer to tell us by Tuesday morning whether that leaves the eight hours available.” Check whether that condition fits the proposed date. If it does not, change the proposal openly and have the appropriate decision maker consider the revised version.
If neither pilot has approval, close the meeting with that outcome. The proposed work has no start date. Engineers continue with their authorized assignments, and nobody books a room, orders equipment or quietly labels offline development as routine maintenance. Record what was considered, how the decision ended and any agreed reason for revisiting it. If a missing board authorization or a disputed voting rule is the obstacle, identify who will obtain the record or arrange appropriate advice, within their authority. If the obstacle is engineering capacity, identify the scheduling fact that would justify putting the question back. A new meeting is worthwhile when it can decide something the last one could not.
Keep other people out of the bargaining. A supplier can answer an authorized question about rental availability without being asked to reserve equipment to make Oren feel committed. A theatre partner can describe its own performance schedule without being recruited to lobby Lia. Employees should be able to report a timing fault without choosing sides, and the museum should never have to surrender a real caption file or visitor data to prove that it wants the feature. Pay, supplier invoices and creditor dealings should continue through their ordinary authorized processes. None belongs in a trade for a founder’s vote.
Give the museum contact a definite time for the next communication if one is authorized and useful. That might be a call before the room booking closes simply to confirm that offline operation remains unavailable for planning purposes. Back inside the company, the founders should be able to answer the engineer who asks, “What am I meant to do tomorrow?” The answer might be to run the approved bench test after the timing fix ships. It might be to finish the timing fix and await a decision. Either answer gives the engineer a real assignment and gives the museum a basis for planning its festival.
Call the conversation that can still help
Before you call another meeting, find out what happened to the decision you already tried to make. Lia and Oren run an Israeli company that makes captioning software for theatres. A museum wants to use it at a festival, including in a basement gallery where the internet connection is unreliable. At a board meeting, Lia proposed assigning two engineers to build a custom offline mode in time for the festival. She voted for it. Oren voted against it. The chair closed the item without announcing an approval. Now the museum producer is waiting for an answer, and one of the engineers has heard that work starts on Monday.
Lia's first call should be to the person who recorded the meeting. What proposal was actually put to the vote? Did it cover the engineers' time, a promise to deliver to the museum, or both? What did the chair say after the votes were counted? Check the account against the notice, the applicable articles, the agreed meeting procedures and any relevant board authorization. Lia and Oren each own half the shares and both serve as directors. That tells you who they are. It still takes a separate inquiry to establish which body can decide this question, whether it had quorum and whether anyone has a casting vote in these circumstances.
They can arrange a conversation with a narrower purpose while those questions are being checked. Oren might call Lia and say, “I'd like forty minutes tomorrow to see whether there's a proposal we could both take back. Can we start with what the museum needs to know by Friday?” Both founders can agree to attend in that capacity. If they need a formal board meeting, the person entitled to convene it should follow the applicable procedure. An invitation to talk over coffee should give neither founder reason to expect a vote.
Keep the people in the room matched to the question. The engineering lead can explain what would happen to the release schedule if two people switched projects. Invite her for that part, if both founders agree and she is authorized to share the information. Let her leave once she has answered. She shouldn't have to sit between her managers while they argue about whose judgment she trusts. The person authorized to speak to the museum can bring the producer's exact request. There may be no reason to invite the producer into an internal discussion about staffing.
Give the meeting a practical order. Read back the stalled proposal, establish the museum's actual deadline, hear the engineering constraints and spend the remaining time on one narrower decision. Reserve the last few minutes to identify who could approve anything that emerges. If nobody can yet answer that question, the conversation can still produce a proposal and a named person to check where it belongs.
Ask the facilitator to keep an offer open
Choose a facilitator both founders are willing to speak freely with. Tell that person what happened at the vote and what the museum is waiting for. Agree beforehand that the facilitator can ask questions, interrupt a circular exchange and read an offer back to the room. Nobody is asking the facilitator to choose a product direction. If Oren thinks the facilitator will decide who is right and Lia expects help finding common ground, settle that difference before discussing a single engineer's time.
A useful first question would be, “What would the museum do differently if it had an answer tomorrow?” Lia knows the producer is deciding where to stage an evening performance. Oren has been treating Friday as the deadline for a finished feature. Once he learns that it is the deadline for choosing a gallery, he asks whether the museum would consider the upstairs theatre, where the current product works. Lia says the basement matters to the production, but admits she hasn't asked whether a prerecorded caption track would serve the one performance planned there. They now have a question someone can put to the producer without promising a build.
Suppose Lia then asks for one engineer to spend half a day testing whether captions will keep playing if a laptop loses its connection. The facilitator asks what result would help. Lia wants to know whether the current software can finish a scene already loaded on the machine. Oren wants the engineer available for a theatre customer's Friday rehearsal. He says, “I could support asking for Thursday morning if the rehearsal fix is already out. I'm still against telling the museum we'll deliver offline mode.” The facilitator reads that back and asks Oren whether “support asking” captures his position. Replacing those words with “approved Thursday” would change what he said.
The engineering lead can explain whether half a day would answer that question and what existing work it would displace. Her estimate supplies a basis for a proposal. It gives nobody permission to book her time. A short test remains a proposal until the appropriate authority approves it. Even an approved test would answer only the technical question it was designed to explore. A laptop that finishes one cached scene may still fail when a caption operator loads the next one.
If a founder changes position, let that founder say how far. Lia might say, “I'd let go of asking for a festival delivery today if we can ask the museum about a single scene.” Ask whether she is withdrawing the earlier proposal, setting it aside for this conversation or simply offering a different route if Oren agrees. Those choices lead to different follow up. Give her room to answer before anybody congratulates the pair on reaching agreement.
Tell the museum what it can rely on
First establish who normally communicates with the museum and what that person is authorized to say. In Lia and Oren's company, the festival account manager has been authorized to coordinate schedules and relay product updates. Lia is a director and usually handles demonstrations. Oren is a bank signatory. None of those facts alone answers who can change the festival commitment. Check the account manager's remit and the existing museum contract before asking her to speak. If a reply could accept a change or affect an existing obligation, get advice on that reply while there is still time to send it.
The producer may need a plain answer that afternoon. Within her authority, the account manager could say, “We haven't approved development of the offline feature, so please don't rely on it when you choose the gallery. Would finishing a scene after a connection drops meet your needs, or do you need the operator to load the whole performance underground? I can check back with you tomorrow morning.” That last sentence is a commitment to make contact. Use it only if she can keep it, including if tomorrow's update is that the company still has no decision.
Listen to the answer before pursuing the smaller test. The producer might say, “The operator has to start the show downstairs. Playing out one scene won't help.” That's worth finding out now. Tell both founders what the producer said, in those terms. A successful test of a loaded scene would give the museum little reason to reserve the basement. The conversation can turn to an upstairs performance using existing capabilities, subject to the museum's agreement and whatever approval that change requires.
The engineers need a different message. Their manager can clarify that the proposed reassignment has not been approved and tell them which existing assignment to follow. If an engineer already spent an hour investigating offline playback because she misunderstood Lia's remark, find out what she did and record it accurately. Don't describe the hour as an approved pilot after the fact. Ask the manager to correct the misunderstanding directly so that the engineer can return to the rehearsal fix without wondering which founder she is expected to please.
Keep the next external update with one authorized contact. Two well intentioned calls can leave the producer trying to reconcile Lia's “we're looking at it” with Oren's “we can't commit.” Ask the account manager to note the producer's deadline, the operational need and exactly what the company said it would do next. The producer needs enough certainty to book a room. She has no need for an account of how either director voted.
Two founders approaching a private mediator can ask what an hour covers and who would attend. For example, Nishri Mediation publishes ₪450 per hour plus VAT per party for family or business mediation with up to three parties. For two parties that is ₪900 per hour before VAT under this particular published rate. Establish who may commission the work, who would pay, and how time spent reading material outside the meeting is charged. Paying for facilitation does not itself approve a commercial trial or change the board record.
Record what happened and what ran out of time
Write the discussion record while people can still correct it. Identify the meeting as a facilitated discussion, name the people who attended and explain when the engineering lead joined and left. Describe the original proposal separately from anything suggested that day. The note should let a manager who wasn't present tell whether anyone authorized work. A reader shouldn't have to infer the answer from a phrase like “broad agreement to explore offline.”
For Lia and Oren, an accurate note might report that Lia proposed a half day playback test, Oren would support submitting it if the rehearsal fix had shipped, and neither founder claimed the discussion approved the test. Record who will check authority, who will ask the producer about starting a performance underground and when each answer is expected. Send the account to both founders for factual corrections. If they disagree about what Oren said, identify the disputed point and invite him to supply his own words. Silence from either founder supplies no missing vote. Keep any later formal minutes tied to the proceeding they actually describe.
Take an expiring option seriously enough to find out what expired. Suppose the producer releases the basement at noon because another production needs it. The next record should say when the room ceased to be available and who confirmed that. It should also distinguish the lost room from the festival contract. Check the contract and ask the producer what can still be arranged before drawing conclusions about the whole engagement. Thursday's proposed test may now have a different purpose or none at all. Ask Lia whether she still wants it considered and why.
A meeting without quorum needs its own account. Suppose the founders arrange a board meeting to consider a revised proposal and a director whose attendance is needed cannot attend. If the applicable requirements leave the meeting without quorum for that item, record attendance and that the item did not proceed to a decision. Ask the person responsible for arranging meetings to check the procedure for another meeting. Don't record the absent director as opposing the proposal. Don't count the facilitated conversation as the missing vote. If the effect of an adjournment or a later meeting is uncertain, have the procedure checked before sending a fresh notice.
A continuing objection calls for a different follow up. Oren may understand the revised plan perfectly well and still believe the festival work would put the rehearsal at risk. Ask him what part he objects to and whether any new fact would change his view. If his answer is no, record it without assigning him another round of persuasion. Where the authorized body has taken a valid decision, record the actual result and his objection accurately. Where no decision was reached, name the unresolved proposal and the next person responsible for addressing it. An objection, an absence and a defeated motion are different events.
Choose the next step within its authority
Negotiation can produce a proposal both founders are prepared to support. It can also reveal that the apparent compromise solves the wrong problem. If the museum needs a cold start underground and the engineers can test only the end of a loaded scene, a facilitator has done valuable work by getting that difference into the open. The founders can stop spending time on that test and ask whether an upstairs performance is still available. The account manager can make the inquiry if it falls within her remit. Committing the company to a revised delivery arrangement is a separate step.
A tie breaker has a different job from a facilitator. Before anyone relies on a chair, adviser or third director to settle the issue, establish whether the applicable articles or agreed procedures actually give that person a role in this decision, on what conditions and with what effect. A respected theatre producer could give a persuasive opinion about what a festival needs. That opinion has no deciding force merely because both founders agreed to hear it. Likewise, a manager's ability to schedule an engineer or a signatory's ability to operate a bank account does not settle the board question.
If the founders disagree about quorum, the scope of a board authorization, the effect of the earlier vote or who may now act, take that specific question to an Israeli lawyer who advises privately owned companies. Bring the current articles, the relevant authorizations, the meeting notice, the actual record and the museum correspondence that bears on timing. Say what the company needs to know before its next contact with the producer. A lawyer can advise on authority and procedure. Any required board or shareholder action still belongs with the appropriate body.
For the next call, keep the request small enough to answer. Lia can say, “Oren, can we spend ten minutes with the account manager confirming what the museum can still book? Then let's read back what each of us is willing to propose and who has to consider it.” Before ending the call, ask the account manager when she will update the producer. Ask the person checking authority when both founders will receive an answer. Read the status aloud once more. If the proposal is still open, say so plainly while everyone who heard the discussion is there to correct the record.
