The Single Issue: a written second opinion on one working relationship
You have asked for the same thing several times, and the response has been the same each time. That is the single issue: one ask, and the response it keeps getting. You are stuck on it, and the question has started to become whether to stay or go.
The Single Issue is a written second opinion on that one thing. The first opinion is the read you already have. One working relationship, one other person, your side only: a co-founder you cannot remove, a 50/50 business partner, a peer on the exec team.
This is for one person. The other person does not take part, does not have to agree to anything, and does not need to know a read exists. Everything in the brief is built from your account, and the brief says so.
Most advice about a relationship like this is built so it can never be wrong: no date, no count, nothing to score. This is built the other way. If the question you keep turning over is some version of "should I stay or go," "is this fixable," "what do I do about a co-founder who is not pulling their weight," those are forecast questions, and a forecast is the one thing an adviser can be held to.
That is why this is called The Single Issue. One ask can be counted. A forecast about one ask, on listed dates, can be checked at the end of the window. A view of the whole relationship cannot be wrong in any way you could show, and I would rather not sell you something that cannot be wrong.
The fee is $2,000, flat. Nothing is paid until three things have happened: your case has passed an arithmetic gate, you and I have spoken, and you have written the account of the situation that the brief is built from. Most cases do not pass the gate, and I say so at the questions, with the arithmetic, before any call.
The brief ends in one change to an ask you already make, which means a different way of asking for something you already want, and a forecast of the response it gets, with a count and dates. You grade the forecast at the end of the window, against what happened, not against how the brief read. If it misses, the second read is free and the miss goes into the published record.
Tell me the single issue in a line or two, the one thing you keep asking for and what happens when you ask: info@johannafarrimond.com. I send five questions back within two business days. Free. Use a role for the other person, never a name. Nothing you send me is privileged, so send nothing you would not want read in a dispute.
info@johannafarrimond.com
On this page: how it works · the gate · a decline, in full · a sample brief, in full · the forecast · the grade · the price
Two reasons to want this
There are two reasons to want this. One is to get the response you have been asking for. The other is to find out whether that response is available at all, because you are weighing whether to stay or go: carry on, buy the other person out, or walk away.
The brief serves both and decides neither. If the forecast is that the response is not coming, and the window bears that out, you hold a dated, counted result about this ask, made to this person, in these weeks. It is not advice to leave, and it says nothing about the other person beyond what they did on the dates the forecast lists. It is one fact you did not have. What you do with it is yours.
How it works
1Five questions, by email. Free.
2A call. Twenty minutes, free, not recorded.
3Your written account. About 45 minutes, in your own words.
4Payment. $2,000, once the account is in. Never before.
5The session. Forty-five minutes, on video.
6The words, confirmed. That reply is the record.
7The brief. Within three business days.
8The window. Thirty days, or 45.
9The check. If the forecast is wrong, the second read is free.
Read the nine steps in full
Five questions, by email. Free. Write a line or two to info@johannafarrimond.com and I send them back within two business days. Use a role for the other person, never a name. Take the time to check dates and count rather than estimate; the count is what the decision runs on. Most cases end here, at the gate, and I tell you which test they failed and why.
A call. Twenty minutes, free, not recorded, accepted cases only. I check the count against your calendar. You check me. And I ask one thing: the brief will give you one change to an ask you already make, in words you agree before I write them down. You will need to make it on every occasion in the window, and there will be at least three. If you already know you will not change how you ask, stop here and pay nothing.
Your written account. About 45 minutes, in your own words, answering a fuller set of questions from me: the ask as you make it, every channel between you, the dated occasions, what you have already tried, what the ask is for. This is the only thing the brief is built from, and the brief quotes it, so everything it stands on is something you can go back and re-read.
Payment. $2,000, once the account is in. Never before.
The session. Forty-five minutes, on video, never recorded by either side. I have drafted the read before it starts. I fill the gaps the draft turned up, then read you what keeps happening as I see it, in counts, and ask whether it matches what you have already seen. Then I read the forecast. You say the ask back in your own words. If you cannot say it, the words change in the room; the ask does not. I do not argue the forecast and I do not ask you to decide anything.
The words, confirmed. After the session I email the ask as agreed. You reply that you can say it. That reply is the record.
The brief. The brief has five parts: the situation as you described it, what you do next each time, why it locks with this particular person, the change, and the forecast. You can read it in one sitting. It arrives within three business days of the session. The sample below is the shape of it. The window starts when it lands, on dates fixed inside it.
The window. Thirty days, or 45 when the calendar needs the extra time to hold three occasions, decided before it opens and never extended after. A window that ends without a grade can be run once more as a new window, which is set out under the grade, below. You make the ask as written and record each response. During the window I answer questions about the count, in writing. Why that is all is set out under the forecast, below.
The check. On the last day of the window, three counting questions, answered by you. The grade follows from the numbers rather than from my judgment. If the forecast is wrong, the second read is free.
Two cases. One I would turn down. One I would take.
Both are composites. Real submissions are confidential and always will be, so these are built from the shape the real ones take rather than from anyone's actual situation. Nobody described below exists.
They are here as a pair because either one alone proves very little. A sample of work anyone can produce. What is harder to produce is the decline, and the decline is the reason the brief means anything.
Before either of them, the arithmetic that separates them.
The gate
Every case is checked for one thing before I take any money: can this situation produce a forecast you could check inside the window.
That reduces to a number, and it is one you read off your own calendar rather than estimate. In the next 30 days, how many times is there an occasion where this could happen at all. If that is fewer than three, the same question for the next 45.
| Where it happens | Next 30 days | Next 45 days | Decision | |
|---|---|---|---|---|
| The case I would turn down | The quarterly board pack | 0 | 0 | Declined |
| The case I would take | The weekly leadership meeting | 4 | 6 | Taken |
Why the floor is three
Four of those meetings are on the calendar in the next month. The next board pack is not, in 30 days or in 45. You can check both numbers against your own diary, which is the point. The decision is arithmetic, not judgment, and it happens before payment.
The floor is three occasions in the window, with at least two of them already on the calendar. Not because three is where a pattern becomes serious; it is often serious at one. Because below three, no forecast can be wrong in a way that means anything. With one occasion, whatever happens looks like a result: a coin landing the way it was always going to land. With two, the only forecast strict enough to mean something is two of two, and one off day on the other side makes it a miss for reasons that have nothing to do with the ask. At three, a forecast of two of three both says something and survives one off day. That is the smallest number at which the grade is honest, and I would rather turn down a real situation than sell a forecast that cannot fail.
Three other things are checked at the same time. Nothing already scheduled would remove the occasion inside the window: a departure, a reorganization, a raise. A scheduled event that raises the cost of the pattern is fine, and is usually why you are writing; one that ends the relationship whatever you do is not, because nothing can be graded against it. What the other person does is something that could be seen or heard, not a trait. And at least one thing in the pattern is something you did, because the forecast changes your side of it.
What I do not take at any count
The gate is arithmetic. This list is not. I decline these whatever the count says, and I say which one applies.
- Harassment, discrimination, or retaliation of any kind.
- Threats, violence, or fear for anyone’s safety.
- Suspected fraud, theft, or any other crime, and anything you are reporting or may report to a regulator.
- Anything already in a legal or HR process, anything where lawyers are exchanging letters, and anything where you are gathering material for one.
- Anything you have a professional or legal duty to report.
- Health, yours or the other person’s, and any urgent personal crisis.
- Relationships that are not working relationships. A family member you run a business with is in scope. A family matter is not.
- A request to assess, diagnose, or investigate the other person. The brief forecasts a response to one ask. It does not describe a person.
These belong with a lawyer, a regulator, a physician, or the police, and a forecast is the wrong instrument for any of them. If one surfaces after I have accepted a case, I stop and say why. If the brief has not been delivered, I return the fee.
The case I would turn down: what happens when it does not clear
The situation in this one is not a small problem. Someone's co-founder is rewriting their contribution before it reaches the board, four times a year, and has been for two years. It is serious, it is real, and the person describing it deserves an answer.
The answer is that I cannot sell them anything they could check.
Read the decline note in full
Sample: a decline note, in full. Composite B. This case is constructed for the page.
Thanks for sending this through. It is a real situation and the kind of work I handle, but I cannot build a forecast from what is here, so I would rather ask than accept and write something you cannot check.
The behavior you describe happens around the board pack, and by your own answer the next one falls outside the coming thirty days. The brief ends in one forecast with a date, and you grade it at the end of the window. For it to be capable of being wrong there has to be something inside the window for it to be wrong about, which is what this process is built around. Here there is nothing, so there would be nothing to grade. I am going to pass for now. There is no charge for this review.
What I am missing is at least three occasions inside the next month where this could surface. You mentioned a weekly one-to-one. Does any version of this pattern turn up there? If it does, reply with what it looks like and I will look again. If not, no problem at all.
Johanna
End of sample.
What was actually declined there
Not the situation, and not the reading of it.
I could tell you what is happening in that case. The pattern is legible, and I would have views about it within an hour. What I could not do is tell you whether those views were right, because at a third of one occurrence a month there is nothing inside the window that would settle it either way.
So the honest description is narrow: I declined the gradeability, not the readability.
That distinction invites an obvious question, and it deserves a straight answer. If the reading is available, why not sell that on its own, for less?
Because a reading you cannot check is worth what readings are worth, and you can get one anywhere, from anyone, at any price. Plenty of people will tell you what is going on with your co-founder. Some of them will be right. None of them will tell you in advance how you would know.
The only thing here that is not already freely available is the part that can fail. Selling the rest without it would be selling the easy half and keeping the money.
If you cannot tell whether your situation would clear the gate, write me a line or two: info@johannafarrimond.com. I send five questions back within two business days and tell you either way, with the arithmetic. Free. Use a role for the other person, never a name. Nothing you send me is privileged, so send nothing you would not want read in a dispute.
info@johannafarrimond.com
The case I would take: what you get
Everything in this brief is built from the account. The person who wrote the account had already tried the obvious asks. What they could not see from inside the situation was which step to change.
Sample: a client brief, in full. Composite A. This case is constructed for the page. No client has received this brief. Dates are illustrative.
Date: 17 August 2026 | Topic: Co-founder decision reopening pattern
Read the account this brief was built from
We have a leadership meeting every Monday afternoon. Over the last two months we have agreed nine things in that meeting that I can list. Every one of them got reopened within a day or three. Not in the meeting. In the engineering Slack channel, or in a direct message to whichever engineer had picked up the ticket. I write the tickets on Monday night after the meeting and they get picked up Tuesday or Wednesday.
At the end of every meeting I ask if anyone has objections. He never does. Then on Thursday in our one-to-one I bring up whatever got reopened and he says we did not really discuss it properly. I have started keeping notes of the meeting and reading them back to him. It does not help. He agrees in the room and it happens again the next week.
The one that made me write this: we agreed infrastructure first for the quarter, no new front-end hires until the migration is done. The next Tuesday he circulated a front-end job description. When I asked, he said it was an expansion of what we agreed, not a reversal.
I read this as him going around me. He is stronger with the engineers than I am and he knows it. It feels like a power move every time, taking the decision to the place where he wins.
We are equal co-founders. I run everything that is not engineering. He runs engineering. There is no fundraising going on, nobody has left, and the board does not meet for another ten weeks. Nothing is on fire. It is just that nothing we decide stays decided, and the engineers are confused about what to build.
What I have tried: asking for objections more directly before we close. Saying "last chance" out loud. Reading the notes back. Pointing out the pattern in the one-to-one. He agrees every time and then it happens again.
1. The situation, as you described it
Over the last eight weeks, across eight Monday leadership meetings, your co-founder has agreed to nine decisions in the room and reopened all nine within 24 to 72 hours. The reopening happens in the engineering Slack channel or by direct message to the engineer holding the ticket. You write the tickets on Monday night and they are picked up on Tuesday or Wednesday. When you ask for objections at the close of each meeting, he raises none. In your Thursday one-to-ones, when you point to the agreement, he says the discussion did not happen properly. In one case he circulated a front-end job description that contradicted an infrastructure-first priority agreed the week before, and described it as an expansion rather than a reversal. You are equal co-founders; you run everything outside engineering, he runs engineering. There is no fundraising, no departure, and no reorganization in progress, and the next board meeting is ten weeks out. Decisions are not overturned; they stall through engineer confusion. You have tried asking for objections more directly, saying "last chance" before closing, reading the meeting notes back, and naming the pattern in the one-to-one. Each produced agreement in the room and the same reopening within one to three days.
2. What you do next each time
You read each reopening as bad faith. Your words: he is "going around me", it is "a power move", he takes the decision to "the place where he wins". On that read, the Monday meeting is the binding venue, the Slack post is a bypass, and "we did not discuss it properly" is a rewrite of the record. So you respond by defending the record: notes read back, the pattern named on Thursday, a firmer close on Monday.
What you do protects something real. You run execution, and execution needs decisions that stay decided. But every version of it presses on the same point, the Monday close, and the Monday close is the one place where the pattern has never shown up. In eight cycles he has objected there zero times. Pressing harder on a step that already produces silence is likely to produce more silence, followed by the same reopening. It also converts a procedural gap into an authority dispute ten weeks before a board meeting, and it shifts the Thursday conversation from what would surface concerns before work starts to whose memory of Monday is correct, which is a dispute with no exit.
3. Why it locks with this particular person
The account supports a different read, and it is the one this brief is built on. Nine reopenings, zero objections in the room, zero messages to you before work started, and every reopening routed to the person holding the ticket, is consistent with a technical review that happens after the meeting rather than in it. The meeting produces assent because a meeting close asks for a decision now. His evaluation of the risk appears to run later, alone, against the details, and when it turns something up he takes it to where the work is. I cannot confirm that from outside. The forecast is built to test it.
If that read is right, it locks like this. You ask for objections in the room; the review has not happened yet, so there are none. The review happens on Tuesday; the concern goes to the engineer. You treat the message as a bypass and relitigate the record on Thursday, which raises the cost of raising concerns after the meeting without lowering the cost of raising them in it. Next Monday, silence in the room again. The lock is structural: a close that demands an answer in real time, meeting a review that runs after the room empties. It does not require bad faith from either of you, and nothing in the account requires it either.
4. The change
Keep the Monday close exactly as it is, and add one step. Mark each agreed decision in the shared log as pending technical review, and say, in the room:
"These are logged as pending technical review. Tickets go out Wednesday morning. If anything needs changing before then, put it in the log or send it to me."
Those are the words you confirmed in writing after the session. The change is yours alone to make. It needs no agreement from him, places no new demand on him, and alters a step you already perform.
What it does: it gives his review a place to land before work starts, on a schedule you set. Tickets currently go out Monday night and are picked up Tuesday or Wednesday. Generating them on Wednesday morning moves the earliest pickup by about a day and the latest by nothing, at a cost of roughly 40 hours between the meeting close and ticket generation. That is the price of the window, and it is paid in the first two cycles whether or not he uses it.
Why Wednesday and not Thursday: his reopenings have arrived 24 to 72 hours after the meeting. A window closing Wednesday morning covers the front half of that range. Thursday would cover nearly all of it, but it pushes pickup to the end of the week, and a window wide enough to catch every reopening you have ever seen would also make a miss say nothing. The window is set short enough that the forecast can fail.
The obvious alternative is to require all objections in the room before anyone leaves. It fails because it demands an immediate evaluation from someone whose evaluation appears to run afterward. More pressure at the close is likely to buy more assent, and the review still happens on Tuesday and still routes to the engineer.
5. The forecast
Graded on 16 September 2026, after that morning's tickets go out, by you, against the three counting questions. A forecast graded wrong earns a second read at no charge, claimed within thirty days of the check.
End of sample.
A note for readers of this sample. This note is not part of what a client receives.
Considered and set aside: asking him to bring concerns to you before he takes them to engineers. Set aside because it is a new demand rather than a change to something you already do, and because the baseline gives it nothing to build on: zero messages to you across nine decisions.
Also set aside: moving ticket generation to Thursday. See section 4. The window would catch more, and a miss would mean less.
How to read the pair
Two things are worth noticing, and they are the two things I would want to check if I were you.
The brief ends in a sentence that can be wrong. A count, a named behavior, dates, and a stated condition under which the read was mistaken. You grade it at the end of the window. If it is wrong, the second read is free, and it goes into the published record as a miss.
The decline turned down money on arithmetic you can verify. That is the part that is difficult to fake, and it is why the brief is worth reading. Anyone can show you their best work. The gate is what makes the best work mean something.
What the forecast is
The brief ends in a forecast: one change to an ask you already make, and the response that change produces, written so that at the end of the window you can count whether it happened. It is set in a box at the end of the brief. The box at the end of the sample above is the complete form, and every brief ends in one like it, with the same seven rows.
What is in the forecast
Where it comes from. The brief opens with the situation as you described it: the ask you already make, in the words you already use, what it reliably produces, and how often, in counts. You have lived this, so you can check it against memory on the spot. In the session I read it back and ask whether it matches what you have seen. If it does not, the read is wrong, and I would rather find that out in the room than at the end of the window. The two sections after that say what you do next each time and why it locks with this particular person. The forecast is built on those three.
The change. One alteration to an ask you already make, chosen because you can make it without the other person agreeing to anything and without telling them a read exists. It is built from your own words and confirmed with you in writing after the session, before it goes in the brief. Never a new demand, never a threat, never a trap. In the sample it is one added step at the close of a meeting you already hold, and one sentence said out loud.
The occasions. The dates inside the window on which you will make the change, listed one by one. There have to be at least three, and at least two must already be on the calendar when the window is set. That is the gate, above, and a case that cannot clear it is declined before anything is paid. In the sample there are four, and the one on the day the brief lands is left out.
The forecast. The response, as something a third party could read off a record, with a time limit and a count: on at least this many of the occasions, this will happen by this point. A note in a log, a message, a date in a calendar. Not a tone, not a mood. In the sample the act is a note in the decision log or a message to you that names one of that Monday's decisions, the time limit is Wednesday morning, and the count is two of four. The forecast can be that the response you want is not coming. That is still a forecast, and it is still graded. For someone deciding whether to stay or go, it is often the more useful answer.
The baseline. What carries on if nothing changes, in the same countable terms, taken from your own history. In the sample: eight meetings, nine decisions, nine reopened, zero concerns raised by any route that reached you first. A prediction with nothing to compare it against is not a forecast; it is a hope with a date on it.
What would make this wrong. The forecast turned around, in the same count. The two rows are written as opposites, so every graded outcome is one or the other. Hit or Miss, nothing in between.
What would make an occasion not count. An occasion that does not happen, happens without the condition the change depends on, or passes without the change made as written, comes out of the count. It does not count against the forecast and it does not count for it. The noun in this label is whatever your occasion is: in the sample, a meeting. If fewer than three occasions count, the forecast is not graded. Not graded is not a grade; it is recorded as not graded and published as such.
What would void the forecast. A change in the situation itself rather than in the counts: one of you on leave for the window, a role change, a departure. A void forecast was never tested. It is recorded as void, and it is not a miss.
During the window. After each occasion, record what happened. Do not argue and do not repeat the ask on the spot; the next occasion is the next occasion. Anything you cannot place as counting or not goes to me in writing and is settled before the last day, never after. There is no coaching during the window and no other support, by design. The test only means something if the ask stays as written, and a forecast I could steer would not be worth grading.
The check. On the last day you grade it, against the three counting questions set out under the grade, below. Hit or Miss follows from the counts. A forecast graded wrong earns a second read at no charge, claimed within thirty days of the check.
The read draws on a behavioral reference I maintain for this work and do not publish. It shapes the read; it does not appear in the brief, and nothing in the brief asks you to take it on trust. What you are buying is the brief and its grade.
One issue, and one person. I take one person per company or family. If two of you want a read on the same situation, it is one of you.
To find out whether your situation can carry a forecast like this one, write me a line or two: info@johannafarrimond.com. Five questions come back within two business days. Free. Use a role for the other person, never a name. Nothing you send me is privileged, so send nothing you would not want read in a dispute.
info@johannafarrimond.com
The grade
Every engagement ends in a sentence that can be wrong.
How the grade is computed, and what each outcome earns
The forecast names an ask and the response it gets. On the last day of the window you answer three questions about what actually happened. How many times the situation came up. How many times you made the ask as written. How many times the response was the one in the forecast. One occasion counts once, however many times something happened inside it. You answer them before I say anything about how the window went, and the grade comes out of those three numbers rather than out of what I think of them.
The rule is in the forecast before the window opens. The forecast is gradeable if at least three occasions count, and an occasion counts only if it happened, with its condition, and you made the ask as written. If you did, and the named response occurred at least the number of times the forecast names, it is a hit. If it occurred fewer times, it is a miss. There is no third grade, because a third grade is somewhere for misses to go. A forecast can also end not graded or void. Both conditions are written in the box before the window opens, and both are counted and published beside the hits and the misses, so neither is somewhere for a miss to go after the fact. The record shows the raw figures for every case, "two of three, threshold two, hit" or "one of three, threshold two, miss," so the difference between a near miss and a clean one is visible without a category to hide it in.
The second question is there on purpose. If the window ran away from you and the ask never got made as written, that is not the forecast being wrong, and it is not graded as though it were. It is recorded as not graded, with the reason.
If it missed, two things follow. The first is a second read at no charge, claimed within thirty days of the check: a new brief, from the same account plus whatever the window produced, ending in a new forecast on new dates. It does not include a further session. If the situation itself has changed, I may ask for one, at no charge. The second is that the miss goes into the published record next to everything else.
A forecast graded wrong is a Miss. Two other outcomes are not grades.
Not graded. A forecast is not graded if fewer than three occasions counted. An occasion does not count if it did not happen, happened without its condition, or passed without the ask made as written. Either way the test did not run, so it can be run once more: the same change and the same forecast, in a new window of the same length, on dates fixed before it opens, at no charge. The new window has to clear the same arithmetic as the first. If it cannot, or if it also ends not graded, the case closes and there is no second read. A forecast is also recorded as not graded if you never send the count, and then nothing further follows, because a new window and a second read both depend on the count. This applies to the first forecast. The window of a second read is the last.
Void. A void forecast was never tested, and it cannot be run again, because the situation it was written for has changed. If the event that voided it was already scheduled, or you told me about it before I accepted the case, I accepted it knowing, and a second read is yours at no charge, on the same terms as after a miss. If the event was not disclosed to me before acceptance, or was something neither you nor I could reasonably have known, there is no second read.
No window is ever extended. A new window is a separate window with its own dates. The first is recorded as not graded, the second as whatever it turns out to be, and both appear in the record.
In every one of these the fee stands. It bought the brief, and the brief was delivered.
Every outcome is published as what it is, beside the hits and the misses.
Results are published once a quarter, misses included, and publication does not depend on the results being good. What gets published is the count, not the case: for each window, the raw figures and the outcome, such as "two of three, threshold two, hit". No sector, no role, no location, no dates, and no wording from any ask or forecast. An update goes out only when at least three new results are ready, and the rows are not in date order, so that no row can be tied to one case. A result that would be alone waits for the next quarter. No situation, no other person, no client, ever. There is no "with your permission" exception, so you will never be asked.
If you do not grade, the forecast is recorded as not graded, and it stays there. The window to claim a second read runs from the day you grade, not from the day the brief arrived.
You keep the brief and the graded appendix, which is the forecast with your three counts and the outcome written in.
There is no track record
What exists instead
No testimonials, no case studies, no client logos, no count of reads delivered. The cases above are composites and say so. If you are looking for evidence that this has already worked for someone like you, it does not exist yet, and this page is not going to imply otherwise.
What exists instead is structure.
The forecast can be wrong, in writing, on a date, and when it fails, the failure is recorded where you can see it. The gate turns down money before it is paid, on arithmetic you can check with a calculator; you watched it do that above. The grade is computed from your numbers, not awarded by me.
None of this is proof. It is the structure that makes proof possible, and hard to fake once it exists.
The price
The fee is $2,000, flat, excluding VAT where applicable. It covers the drafting, the session, the brief within three business days, the counting channel through the window, the check, and the graded appendix. The five questions and the call cost nothing, whichever way the decision goes, and nothing is paid before your account is written.
What your side involves, and what the fee does not buy
Your side of it is five sittings: the questions, the call, the written account, the session, and the count at the end of the window. And one line by email to confirm the words. Nothing on this page expires, and there is no counter on it.
The fee buys the brief. It does not buy the outcome, and it is not returned if you decide not to make the ask. If the account has not arrived within 30 days of the call, or payment has not followed within 30 days of the account, the case closes and what you sent is deleted.
What this is not
Not legal advice, not mediation, not therapy, not coaching
Not legal advice, and not privileged: I am not a lawyer. What you send me and what I send you, including your written account and the brief, is not protected by legal privilege and could be demanded in a dispute. If that matters in your situation, ask your lawyer before you write to me. Not mediation: I do not contact the other person, and nothing reaches them from me or through me. Not therapy. Not a verdict on the other person: the brief does not ask whether they are decent. It forecasts what they do in response to one ask, on listed dates. Not coaching: one brief, one forecast, one grade, and then the work ends. There is no retainer and no program of sessions. Not ongoing work: the engagement ends at the check, unless a missed forecast earns the free second read or a forecast that was not graded is run once more. What I decline at any count is listed under the gate, above.
Working relationships only. If the other person is family, it is the business between you that gets read, not the family.
And it is your side only. Nothing is collected from the other person. You refer to them by a role or a label, never a name, from your first email on. Nothing identifying them is wanted or kept. I keep your written account for no more than 200 days and the brief for three years, and then both are deleted. The privacy notice has the detail. They are never named, scored, or typed, and what they think stays unresolved; the brief says so where it matters.
Who does the work
One person, and what she did before this
One person: Johanna Farrimond. Physics and electrical engineering degrees. An MSc in Information Assurance. Twenty years in IT consulting, a decade of it in classified government networks. My job was to say in writing what a system would do under load or under failure, before it did it, and someone had to act on what I wrote.
Forecasting a network and forecasting a request between two people are different problems. What carries over is the discipline: state what will happen, with a date and a count, and publish whether it did.
I wrote these for my own decisions before I sold one, dated, then graded against what happened. The process has not changed.
How to start
Write me a line or two: the one thing you keep asking for, and what happens when you ask. I send five questions back within two business days. One of them asks you to open your calendar and count the occasions in the next 30 days, because that is the number the gate runs on. The questions are free and so is the call that follows them.
Then one of two things. It fits, and I say so, and the questions for your written account follow. Or it does not, and I tell you why, with the arithmetic, the way the case above was declined. A decline costs you nothing.
Tell me the single issue in a line or two: info@johannafarrimond.com. Use a role for the other person, never a name. Nothing you send me is privileged, so send nothing you would not want read in a dispute. info@johannafarrimond.com