First time we ran Orchestrator in front of a client, and what went wrong
D
Discli@homelandtinted · Product marketer
We have used the launch content workspace internally for months, on the team account. This week we ran it live in a client meeting for the first time. Researcher, brief writer, copywriter, reviewer. The reviewer returned the draft automatically (as designed) and the client saw 'RETURN' in the log and thought the system had failed. It had not; it had done exactly what we told it. Lesson: explain the return loop before pressing run. The second run, after the revision, got the approval and the client relaxed.
What went well: the client asked for the run log export, which is a first.
4 REPLIESOP
Owen Park@meadowtypeset · Design systems lead
We had the same reaction internally. Now I say 'watch for the return, that is the reviewer doing its job' before every demo.
M
Merayalbe@hikeconcurrent · Agent builder
The export request is the win. A client who wants the log is a client who will trust the next run.
A
Aris@academydevilish · Instructor
Adding 'explain the loop before the demo' to the clinic notes. Thank you for posting the awkward version.
D
Discli@homelandtinted · Product marketer
Client signed off the second run this morning. Awkward version worth it.