Two people say Friday

A customer has been asking to search old invoices by purchase order number. Mara promised to come back with a date as soon as she had one. She joins the release call with a half-written email open. All it needs, as far as she knows, is the day the customer can try it.

Kit has been testing the search on newer invoices. The older records are a different matter. Ellis, who runs the release, has ten minutes to check the plan before the next team needs the room.

Release check-in
  1. Kit · Engineer

    I can have it ready Friday. I’ve got the older invoices running through overnight.

  2. Mara · Account lead

    Brilliant. I’ll tell the customer they can try it Friday afternoon. They’ve been chasing me for a date.

  3. HintAlong · Only Ellis sees this

    Ask who can use invoice search on Friday.

  4. Ellis · Release lead

    Hang on before you send that, Mara. On Friday the 12th, if I sign in as that customer and look for an old invoice, what will I see?

  5. Kit · Engineer

    Their usual screen. The 12th is when I can give support a build to test. I want them to try the old purchase orders that failed last time.

  6. Mara · Account lead

    Oh. I had that down as the day the customer could search. Good thing the email’s still open.

Put a person on each date

“Ready” made sense on Kit’s side of the table. It meant support could finally try the tricky records on a test account. Mara heard the same word from the other end of the process, where a customer is waiting for an answer. Asking what shows up on the customer’s screen lets Kit explain the gap without anyone having to defend their calendar.

Ellis draws two little boxes on the board. In the first he writes “Support tries old invoices.” He leaves the second empty. A customer date belongs there eventually. There’s a piece of work between the two boxes that could still change the second date.

Would saying the date twice have helped?

Ellis “Quick check before we go. We all heard Friday the 12th?”

Kit “Yes, the 12th works for me.”

Mara “Same here. I’ll let them know.”

Everyone can read the same square on the calendar. Kit and Mara would still leave expecting different people to be able to use search that afternoon.

Mara asks for something she can put in the email today. She’d rather make one promise she can keep than ask the customer to hold another afternoon free.

  1. Mara · Account lead

    Can I tell them when they’ll hear from me, even if we don’t have a go-live yet?

  2. Kit · Engineer

    Yes. Support tests on the 12th. On Monday I’ll tell you how those older orders did. If they pass, we can talk about opening the pilot on Friday the 19th.

  3. Ellis · Release lead

    I’ll put the 19th down as a possible pilot. Mara, Monday’s update is yours to send either way.

The note sales can use

Ellis reads back the note with the dates and owners in it. Mara can lift the middle line straight into her email. Kit can recognise what he agreed to deliver, including the test that has to happen first.

Release note

Invoice search pilot

Friday the 12th
Support gets the test build. Try the older invoices with purchase order numbers that previously failed.
Monday update
Kit reports the test result to Mara. Mara updates the customer that day, including any work still open.
Friday the 19th
Earliest proposed customer pilot. Ellis will confirm access after support reviews the results and the team agrees to open it.

Mara takes the invitation to try search out of her draft. She can now tell the customer exactly what support is checking on Friday and when she’ll be back in touch.