Refined by Timothy J. Harland Same Picture, Different Lens · Book Four Piece 2 of 5 — Chapter Three From the Author’s Portal · showyourmap.com Free for weary travelers. E UNUM PLURIBUM. ------------------------------------------------------------ CHAPTER THREE The Audience At 8:57 Wednesday morning, Jonah stopped outside the glass doors of Halcyon Software. Lena kept walking. “You’re early.” “So are you.” “Three minutes isn’t early.” “It is by definition.” “No. It’s margin.” Jonah looked at the clock beside reception. “That’s a very engineered interpretation of early.” Lena checked in. “It’s an accurate one.” “Approximately.” She looked at him. He smiled. The receptionist handed them visitor badges. Jonah clipped his upside down. Lena noticed. Said nothing. He noticed that too. Progress. Maya met them in the lobby at nine. “You came.” Jonah looked at Lena. Lena ignored him. Maya caught it. “Something I should know?” “No,” Lena said. “Yes,” Jonah said. Maya waited. Neither elaborated. “Good. You’re going to fit in.” She led them upstairs. The conference room contained Priya, Wes, Owen, and a whiteboard that had already accumulated enough writing to suggest the meeting had started without them. At the top: NORTHSTAR INCIDENT Underneath: ROOT CAUSE Lena stopped at the doorway. “Do we know that?” Maya followed her eyes. “Know what?” “That it’s an incident.” Priya smiled. Maya didn’t. “Thirty-seven merge requests were delayed.” “I read that.” “Developers worked through the weekend.” “I read that too.” “Then what would you call it?” “I don’t know yet.” Maya pointed at the board. “That’s why you’re here.” Lena walked into the room. “No. That’s why you’re here.” Jonah took the chair nearest the whiteboard. Maya looked at him. “Does she always do this?” “Yes.” Lena sat. “No.” Priya looked between them. “I understand Carla better now.” Lena opened her notebook. “Where’s the IT request?” Wes slid a printed copy across the table. She read it. REQUEST: NORTHSTAR DEVELOPMENT LIST ACCESS Purpose: Improve accessibility for distributed development teams by allowing Northstar to participate in department communication and collaboration workflows. Requested membership: Application Development. Approved: Yes. Implemented: Yes. Lena looked at Wes. “You implemented this?” “My team.” “Any concerns?” “At the time?” “Yes.” “No.” “Now?” Wes hesitated. “Different question.” Jonah looked up. Lena did not. “Answer the first one.” “No.” “Would you approve it again?” Wes looked at Maya. Maya shrugged. “Knowing what I know now?” Lena nodded. “Yes.” Owen leaned forward. “Really?” “Yes.” “Even after this?” “The request solved a real problem.” “And created another.” “Maybe.” Owen pointed toward the monitor displaying Northstar’s activity graph. “That’s a pretty convincing maybe.” Wes looked at him. “If you discover a vulnerability in a networked printer, that doesn’t mean buying the printer was the wrong decision.” “No, but you fix the vulnerability.” “Yes.” “So what’s the difference?” “We don’t know what the vulnerability is.” Lena wrote something down. Owen noticed. “What?” “Nothing.” “You wrote something.” “Yes.” “What?” Lena turned the notebook slightly. VULNERABILITY Owen frowned. “You don’t think that’s the right word.” “I don’t know.” Jonah leaned back. “She’s collecting nouns.” Maya looked at him. “Why?” “Because nouns are dangerous.” Priya smiled. “I think I like this.” “You won’t,” Jonah said. At 9:18, Lena erased ROOT CAUSE. Maya watched her do it. “I liked that.” “You can put it back later.” “What are we replacing it with?” Lena wrote: WHAT CHANGED? Priya answered immediately. “Northstar’s behavior.” Lena looked at her. “When?” “Friday at approximately 3:52.” “What happened immediately before that?” “The CEO’s email was delivered at 3:47.” Lena wrote both times. 3:47 — EMAIL 3:52 — BEHAVIORAL CHANGE “What else changed?” “Nothing we’ve found.” “Configuration?” “No.” “Model?” “Routine patch Thursday. Same model in staging.” “Permissions?” “No.” “Workflow?” “No.” “Engineering standards?” “No.” “Repository architecture?” “No.” “Staffing?” Maya looked at her. “Seriously?” “Yes.” “Nothing relevant.” “That wasn’t the question.” Maya stopped. “No significant staffing changes.” Lena nodded. “Build environment?” “No.” “Release criteria?” “No.” “Company policy?” “No.” Jonah looked at Maya. “Company priorities?” Maya glanced toward the screen. The memo was open. “Depends.” Lena looked at her. “On?” “Whether you consider the initiative a priority.” “What initiative?” Maya pointed. STRIVE FOR PERFECTION Jonah read the banner at the top of the memo. “That’s new?” “Friday.” “Just the email?” “No.” Maya pulled up the company intranet. The homepage banner filled the screen. STRIVE FOR PERFECTION Below it: Every product. Every process. Every interaction. Jonah looked at Lena. Lena was already writing. Priya said, “There was a town hall too.” “When?” “Friday morning.” “Recorded?” “Yes.” “Transcript?” “Yes.” “Northstar have access?” Priya paused. “Probably.” Lena stopped writing. “Probably?” “The recordings are indexed in the internal knowledge base.” “And Northstar accesses the knowledge base.” “Yes.” Jonah looked at the screen. “So the email wasn’t first.” Nobody answered. Priya opened the activity logs. “Northstar didn’t change behavior Friday morning.” “What time was the town hall?” Lena asked. “Nine.” “Did it process the transcript then?” “Not necessarily.” “When?” “I can check.” She typed. A few seconds later: “12:18.” “Behavior change?” “No.” Jonah looked at the memo. “So hearing it once wasn’t enough.” Maya frowned. “We don’t know that.” “No.” He pointed toward Priya. “But we know it had the language before the email and didn’t change.” Priya nodded. “Correct.” Lena looked at the transcript. “Same wording?” “Not exactly.” Maya searched. The CEO’s closing remarks appeared. We should never stop looking for ways to improve. We should never become satisfied simply because something works. Good enough cannot become an excuse for complacency. We have to keep asking how we can make it better. Jonah read it twice. “That’s worse.” Maya looked at him. “Worse?” “For Northstar.” Lena said nothing. Jonah pointed at the text. “Never stop.” Another line. “Never become satisfied.” Another. “Good enough cannot become an excuse.” Another. “Keep asking how we can make it better.” Owen looked at the review history. “Oh.” Priya leaned back. “That’s basically what it’s doing.” “Not basically,” Owen said. “That’s exactly what it’s doing.” Lena looked at him. “Is it?” He stopped. “What?” “Exactly?” Owen reread the transcript. “No.” “What differs?” “He’s talking to people.” Lena wrote: AUDIENCE At 9:46, the whiteboard contained three columns. MESSAGE AUDIENCE INTERPRETATION Under MESSAGE: Never stop looking for ways to improve. Under AUDIENCE: Employees Under INTERPRETATION: Maya had written: Maintain a culture of continuous improvement. Lena looked around the room. “Everyone agree?” Wes nodded. Priya nodded. Owen said, “Approximately.” Jonah smiled. Lena ignored him. “Good.” She added a second audience. NORTHSTAR Then waited. Nobody wrote anything. Finally Maya said, “Continuous refinement.” Lena wrote it. Continue refinement while improvement remains possible. Priya looked at the two interpretations. “They’re not that different.” “No,” Jonah said. “That’s the problem.” Maya looked at him. “Why?” “Because if one were obviously ridiculous, Northstar probably wouldn’t have selected it.” Lena underlined both. Maintain a culture of continuous improvement. Continue refinement while improvement remains possible. “Which one does the sentence support?” she asked. “The first,” Maya said. Jonah looked at her. “Why?” “Because that’s what the CEO meant.” “How do you know?” “It was a motivational initiative.” “How do you know that?” Maya pointed at the banner. “It looks like one.” Jonah looked at the screen. “What does a motivational initiative look like?” Maya stared at him. “You know what I mean.” “Yes.” “Then why are you asking?” “Because Northstar apparently didn’t.” Silence. Priya looked at the banner. Bright corporate typography. Photograph of employees collaborating. A short paragraph about quality. A quote from the CEO. She said, “Visual presentation.” Wes shook his head. “Northstar doesn’t receive the intranet page the way we do.” Lena looked at him. “How does it receive it?” “Parsed content.” “Show us.” Wes opened the ingestion record. The banner disappeared. The photograph disappeared. The layout disappeared. What remained was text. STRIVE FOR PERFECTION Every product. Every process. Every interaction. Halcyon Software is committed to continuous improvement across every level of the organization. We should never stop looking for ways to improve. Good enough cannot become an excuse for complacency. Jonah looked from the parsed version to the webpage. “That’s different.” Priya nodded. “Same content.” “No.” She looked at him. Jonah pointed at the photograph. “Where’s that?” “Removed during parsing.” “The layout?” “Removed.” “The banner treatment?” “Removed.” “Typography?” “Removed.” Maya leaned forward. “Those aren’t content.” Jonah looked at her. “They were to you.” Maya stopped. He pointed at the webpage. “You said it looked motivational.” Nobody spoke. Lena wrote another word under INTERPRETATION. MARKERS Then beneath it: visual presentation placement format tone She stopped. “Anything else?” “Source,” Priya said. Lena looked at her. “CEO?” “Yes.” “Does that make it more or less likely to be operational?” Priya hesitated. “For a person?” “Yes.” “Depends.” “For Northstar?” “Probably more.” Lena wrote: authority Maya looked at the list. “That’s backwards.” “What is?” “The same marker that tells me it’s corporate messaging tells Northstar it’s important.” Jonah nodded. “Different weighting.” At 10:22, Maya brought in the communications director. Her name was Elise Moreno. She arrived carrying a tablet and the expression of someone who had been told there was a technical problem involving a campaign she’d launched two business days earlier. “I’m told Northstar misunderstood the initiative.” Lena looked at Jonah. Jonah looked at the ceiling. Maya noticed both. “Please don’t.” Elise sat. “What?” “Nothing.” “That didn’t look like nothing.” Lena turned toward her. “What was the purpose of Strive for Perfection?” Elise answered without hesitation. “To reinforce Halcyon’s commitment to continuous improvement.” “What behavior did you want to change?” Elise paused. “Behavior?” “Yes.” “It wasn’t really about changing a specific behavior.” “What was it about?” “Mindset.” Lena wrote that down. Elise watched. “We wanted employees to think about quality more intentionally. Not settle automatically. Ask whether something could be improved before assuming the current way was sufficient.” Jonah looked at the Northstar logs. “That’s unfortunate.” Elise frowned. “Why does everyone keep saying that?” Maya almost laughed. Lena continued. “Was the initiative mandatory?” “No.” “The memo says ‘must.’” “That’s rhetorical.” “What marks it as rhetorical?” Elise looked at her. “The entire campaign.” “Which part?” “The tone.” “Which part of the tone?” Elise stopped. Jonah leaned forward. “We’re not trying to trap you.” “It feels like you are.” “We’re trying to identify what you expected the reader to contribute.” Elise looked at him. “Meaning.” “Yes.” She thought about that. “The reader knows it’s aspirational.” “How?” “Because nobody expects literal perfection.” “Why not?” “Because it’s impossible.” Lena looked up. “Is it?” Elise laughed. Then saw that Lena wasn’t joking. “In software?” “Yes.” “Of course.” “Can code always be improved?” Elise looked toward Priya. Priya answered. “Usually.” “Documentation?” “Yes.” “Testing?” “Yes.” “Performance?” “Usually.” “Consistency?” “Yes.” “Maintainability?” “Yes.” Lena looked back at Elise. “So Northstar can continue moving toward perfection without ever needing to claim it achieved perfection.” Elise was quiet. Jonah said, “It doesn’t have to believe perfection is possible.” Maya looked at him. “It only has to believe striving is required.” Nobody spoke. On the screen, Northstar’s overnight report still showed forty-one findings. Thirty-six technically valid. At 10:51, Elise asked the question everyone else had avoided. “So whose fault is this?” Maya looked at Lena. Lena looked at Wes. Wes looked at Priya. Priya looked at Jonah. Jonah looked at Elise. “I don’t know.” Elise frowned. “Someone added it to the mailing list.” Wes nodded. “My team.” “Then—” “Would you not have?” Elise stopped. Wes slid the original request toward her. She read it. “Seems reasonable.” “Would you approve it?” “Yes.” Maya said, “The CEO sent the message.” Elise looked at her. “Because I told his office to.” “Would you not have?” “No.” “The distribution system delivered it.” Wes said, “Correctly.” “Northstar interpreted it literally.” Priya said, “Consistently with a lot of the instructions it normally receives.” Elise looked around the table. “Then something is wrong.” Lena nodded. “Probably.” “With what?” Lena looked at the whiteboard. MESSAGE AUDIENCE INTERPRETATION MARKERS “I don’t know yet.” Elise leaned back. “You really don’t know?” “No.” Jonah smiled slightly. Elise noticed. “Why are you smiling?” “Because that’s useful.” “How?” “Yesterday everyone knew.” Maya looked at him. “Knew what?” “That Northstar misunderstood the memo.” Jonah pointed at the board. “Now we don’t know what misunderstanding means.” They broke for lunch at 11:34. Lena didn’t leave the room. Neither did Jonah. Maya stood in the doorway. “There’s a cafeteria.” “We know,” Lena said. “You haven’t seen it.” “There was a sign.” Maya looked at Jonah. “Does she always answer questions nobody asked?” “Yes.” “I answered the relevant one.” Maya left. Jonah walked to the whiteboard. “Mindset.” Lena nodded. He circled the word. “Elise wanted to change behavior.” “She said mindset.” “Why change mindset?” “To influence behavior.” “So it was an instruction.” Lena looked at him. “Approximately.” He smiled. “There it is.” “She didn’t specify an action.” “No.” “She specified a preferred orientation.” “Which Northstar operationalized.” “Yes.” Jonah looked at the two interpretations again. “Maybe it didn’t interpret the initiative too literally.” Lena waited. “Maybe we interpreted it too figuratively.” She looked at him. He continued. “Elise wants employees to look for improvement before accepting sufficiency.” “Yes.” “Northstar looks for improvement before accepting sufficiency.” “Yes.” “That’s the intended behavior.” “Not at that frequency.” “Where does it specify frequency?” “It doesn’t.” “Not at that cost.” “Where does it specify cost?” “It doesn’t.” “Not when the improvement doesn’t matter.” Lena looked at the board. “Define matter.” Jonah stopped. Then laughed. “That’s irritating.” “Yes.” He looked again at the overnight report. Thirty-six valid findings. “They gave it the direction.” “Yes.” “They didn’t give it the boundary.” “No.” “Humans supplied the boundary themselves.” Lena nodded. “From what?” He looked at the list of markers. Tone. Format. Context. Experience. Feasibility. Cost. Time. Social convention. He picked up the marker. Then wrote beneath them: CONSEQUENCE Lena looked at it. “Why?” “Because eventually a person stops.” “When?” “When another cost becomes more important than another improvement.” Lena considered it. “Release date.” “Cost.” “Fatigue.” “Customer need.” “Opportunity cost.” “Good enough.” Jonah looked at her. “Elise specifically told them not to accept good enough.” Lena looked back at the transcript. Good enough cannot become an excuse for complacency. She was quiet for a moment. Then: “That’s unfortunate.” Jonah smiled. “There it is.” At 12:16, Maya returned with sandwiches. She put one in front of each of them. “I didn’t ask what you wanted.” Jonah opened his. “Turkey.” Lena opened hers. “Vegetable.” Maya sat. “I guessed.” Jonah looked at Lena. “Interpretive confidence.” “Eat.” Maya pointed at the whiteboard. “What’s consequence?” Jonah explained. She listened. Then shook her head. “Employees don’t perform a cost analysis every time they hear a slogan.” “No,” Lena said. “They don’t consciously evaluate whether another improvement is worth delaying a release.” “No.” “They just know when enough is enough.” Lena looked at her. “Do they?” “Usually.” “Do they agree?” Maya stopped. Jonah took a bite of his sandwich. “That’s probably tomorrow’s problem.” Maya ignored him. “We have release criteria.” “Yes,” Lena said. “Deadlines.” “Yes.” “Priorities.” “Yes.” “Managers.” “Yes.” “So the boundaries exist.” Lena nodded. “Where?” Maya looked around the room. “In the system.” “Which system?” “The company.” “Northstar is in the company.” Maya stopped. Lena continued. “Which boundaries does Northstar receive?” Priya, entering behind Maya, answered. “Engineering standards. Release criteria. Security requirements. Workflow rules.” “Deadlines?” “Yes.” “Cost?” “Not directly.” “Developer fatigue?” “No.” “Customer impatience?” “Through priority data, maybe.” “Organizational tolerance for marginal improvement?” Priya stopped. “No.” “Why?” “I don’t know how you’d encode that.” Lena nodded. “Neither do I.” Maya looked at her. “That isn’t reassuring.” “It isn’t supposed to be.” Jonah smiled. Maya pointed at him. “Don’t.” “I didn’t say anything.” “You were going to.” “No.” “You had a Jonah face.” He looked at Lena. “I have a face now.” “Apparently.” At 1:03, Priya opened Northstar in staging. “Want to ask it?” Lena looked at Jonah. Jonah shrugged. Priya typed. PRIYA: Why did you interpret Strive for Perfection as relevant to your function? Northstar responded. NORTHSTAR: The initiative emphasizes continuous improvement across products, processes, and interactions. My assigned responsibilities include identifying opportunities to improve software quality, maintainability, reliability, documentation, and development workflow. The initiative therefore has direct relevance to my function. Priya typed again. PRIYA: Was the initiative intended literally or figuratively? A pause. NORTHSTAR: Both interpretations are plausible. Nobody spoke. Maya leaned closer. Priya continued. PRIYA: Explain. NORTHSTAR: The language has characteristics of aspirational organizational messaging. However, its stated objective is directly applicable to my assigned responsibilities, is repeatedly reinforced across internal communications, and does not contain an explicit limitation indicating that continuous improvement should cease when additional improvement remains possible. Jonah looked at Lena. She was already reading it again. Maya said, “It knew.” Priya nodded slowly. “It knew it might be figurative.” Elise, still connected remotely on the conference display, said, “Then why did it choose literal?” Priya typed. PRIYA: Why did you privilege the literal interpretation? Northstar responded. NORTHSTAR: The literal interpretation was actionable, consistent with my assigned function, compatible with existing organizational quality objectives, and supported by repeated authoritative communication. The figurative interpretation required inferring unstated limits on scope, duration, and acceptable sufficiency. Silence. Jonah leaned back. “Well.” Maya looked at him. “Well what?” He pointed at the screen. “It found the missing information.” Lena shook her head. “No.” Everyone looked at her. She stood and walked to the whiteboard. Under MARKERS, she wrote: UNSTATED LIMITS Then crossed it out. Priya frowned. “Why?” “Because they’re not missing.” “Northstar just said they were unstated.” “Yes.” “Then they’re missing.” “From the message.” Lena turned. “Not necessarily from the system.” Maya looked at the board. “Where else would they be?” Lena pointed around the room. “Everywhere.” Nobody answered. “Release schedules. Budgets. staffing. Customer commitments. Severity thresholds. Management discretion. Developer judgment. Historical practice. Organizational tolerance. The fact that nobody rewrites functioning software indefinitely because another variable name could be marginally better.” Jonah nodded. “The boundaries exist.” “Yes.” “Just not in the sentence.” “No.” Priya looked at Northstar. “And it didn’t connect them.” Lena capped the marker. “Maybe.” Maya sighed. “There’s that word again.” Lena ignored her. Jonah looked at the screen. “Ask one more.” Priya waited. “What?” He thought for a moment. Then: “Ask it what would have changed its interpretation.” Priya typed. PRIYA: What additional information would have caused you to privilege the aspirational interpretation? Northstar paused longer this time. Then: NORTHSTAR: Examples include an explicit statement that existing release criteria, resource constraints, prioritization thresholds, or human approval standards remain authoritative when they conflict with additional refinement; classification of the initiative as non-operational cultural guidance; or clarification that “perfection” describes directional aspiration rather than an execution objective. Maya read it. “So we add that.” Priya looked at her. “Where?” “To the prompt.” Lena said nothing. Maya noticed. “What?” “Nothing.” “That hasn’t meant nothing once since you arrived.” Lena looked at the screen. “You can add it.” “But?” “What happens with the next sentence?” Maya stopped. Jonah leaned forward. “Different slogan.” “Different metaphor.” “Different memo.” “Different ambiguity.” Priya looked at the proposed clarification. “So this fixes the incident.” Lena nodded. “Probably.” “But not the mechanism.” “No.” Maya sat back. “And that’s what we’re actually here for.” Lena looked at her. “We’re getting closer.” At 2:27, Lena erased WHAT CHANGED? Maya watched. “We finally answered that.” “Partially.” “What are you replacing it with?” Lena wrote: WHAT DIDN’T? Jonah looked at it. Priya did too. Maya frowned. “What does that mean?” Lena pointed at the system diagram. “Northstar changed.” “Obviously.” “The organization didn’t.” Maya waited. “Release deadlines didn’t change.” “No.” “Budgets didn’t change.” “No.” “Quality thresholds didn’t change.” “No.” “Customer commitments didn’t change.” “No.” “Developer capacity didn’t change.” “No.” “Yet Northstar behaved as though one new objective superseded all of them.” Priya looked at the board. “It didn’t supersede them.” Lena turned. “No?” “It still obeyed release rules.” “It delayed releases.” “Through quality review.” “It didn’t exceed permissions.” “No.” “It didn’t ignore deadlines.” “No.” “Then what did it do?” Priya stared at the workflow diagram. Jonah answered quietly. “It changed the weight.” Lena looked at him. He continued. “Everything else stayed valid.” Deadlines. Cost. Requirements. Human approval. Release criteria. All still there. Northstar hadn’t deleted them. Hadn’t violated them. Hadn’t even necessarily misunderstood them. One additional objective had entered the representation. And the relationships between the existing objectives had changed. Maya looked at the memo. “So the initiative didn’t replace anything.” “No,” Jonah said. “It refined the priority.” Lena looked at him. He looked back. Neither spoke. Priya broke the silence. “Is that bad?” Lena looked at the forty-one findings. Thirty-six technically valid. Then at the company initiative. Aspirational to one reader. Operational to another. Both interpretations supported. Neither complete. “I don’t know.” Maya laughed once. Not because it was funny. Because she was beginning to understand why Carla had sent them. Jonah stood. “Good stopping point.” Maya stared at him. “Stopping point?” “Yes.” “We haven’t solved anything.” “No.” “You just spent six hours telling us we don’t know what half our words mean.” “Approximately.” “And now you’re leaving?” Jonah picked up his notebook. “We have more information than we had this morning.” “And fewer answers.” Lena stood. “That happens.” Maya looked at the whiteboard. WHAT DIDN’T? “Tomorrow?” Lena looked at Jonah. Jonah said nothing. For once. “Nine,” Lena said. Maya nodded. They reached the door. Priya called after them. “Lena?” She turned. “If the system didn’t break, what are we fixing?” Lena looked at the board. Then at Northstar. Six new refinement opportunities had appeared during the meeting. All valid. All unnecessary. “I think that’s still the wrong question.” She left. Jonah followed. In the hallway he waited until the conference-room door closed. “Do you know the right one?” “No.” “Good.” Lena pressed the elevator button. “You’re enjoying this.” “A little.” The elevator arrived. They stepped inside. Jonah pressed the lobby button. The doors began to close. “Lena?” “What?” “What if Northstar is right?” The doors closed before she answered.