A Reviewed Observation Log, Not an Open Door or No Practice: Answering Newcomers' First-Ninety-Day Questions About How a Team Works

Abstract

We followed 487 newly hired employees in 64 teams across eight organizations through their first year. In "reviewed-log" teams, newcomers kept a short record of team practices that puzzled or surprised them during their first ninety days, and team leads went through it with them at days 60 and 90, with any item left open due a recorded response within four weeks (n=171). In "open-door" teams, newcomers were told they could raise anything at any time (n=168), and in "no-practice" teams, nothing was said either way (n=148). Reviewed-log newcomers recorded 7.4 items on average; 63% were answered with an explanation, 9% led to a change, 7% to a trial of an alternative, and 21% went unanswered. At six months, reviewed-log newcomers rated how far their perspective was valued at 5.3/7, against 4.5/7 for open-door newcomers (an 18% gap) and 4.3/7 for no-practice newcomers (a 23% gap). Among reviewed-log newcomers, this rating was similar whether none of their items had led to a change (5.2/7) or at least one had (5.4/7). In reviewed-log teams, every credited change arose from a logged item. Practice changes credited to a newcomer's observation within six months came to 0.67 per newcomer in reviewed-log teams, 0.54 in open-door teams (a 24% gap), and 0.52 in no-practice teams (a 29% gap). Team leads spent 3.4 hours per newcomer on the reviews, and at three months existing team members in reviewed-log teams felt more second-guessed (3.9/7, against 3.2/7 and 3.1/7), a difference gone by twelve months.

1. Introduction

Folk wisdom about joining a team says to keep quiet for the first few months, learn how things are done, and save the questions until you have earned the right to ask them. A more recent version of the same advice runs the other way and tells organizations to value newcomers' "fresh eyes." Both versions describe what the newcomer should do. Neither says much about what the team does with what the newcomer sees.

What newcomers see is often worth having. In their first weeks they notice practices that long-serving staff stopped noticing years ago, and they lose that view quickly as the practices become their own. But a newcomer's question about a practice is also, to the people who built it, a small challenge, and a newcomer whose early questions go unanswered may stop asking, whatever the answer would have been.

Two of the practices we compared ask newcomers to speak; one also commits the team to answer. We define each in turn below and report what each produced for the newcomer, for the team's practices, and for the people already there.

2. Method (Summary)

Eight organizations (two software companies, an engineering firm, a hospital's administrative divisions, a regional bank, a university's professional services, a logistics firm, and a public housing provider) took part. Teams were classified by the onboarding practice their leads reported and that onboarding records confirmed, and every new hire to those teams over a twelve-month window was invited; 487 of 552 invited newcomers enrolled.

A reviewed-log team is one where the newcomer kept a log. Newcomers in these teams recorded, during their first ninety days, any team practice that puzzled or surprised them, in a sentence or two. At day 60 and day 90 the team lead went through the log with them, and each item was recorded as explained, changed, set for a trial of an alternative, or left open; items left open were to receive one of the other responses within four weeks, and items still open after four weeks were counted as unanswered (23 teams, n=171 newcomers). An open-door team is one where the lead told newcomers in writing, during their first week, that they could raise any question about how the team worked at any time, with no log or scheduled review (22 teams, n=168). A no-practice team is one where neither was in place (19 teams, n=148).

Newcomers rated how far "my perspective is valued on this team" (1–7) at three, six, and twelve months. Practice changes credited to a newcomer came from team change logs, which in all eight organizations recorded who had raised the issue behind each change; we counted changes within six months of the newcomer's start that credited that newcomer. Leads logged the time they spent on reviews. Existing team members rated at three and twelve months how far "our ways of working are being second-guessed" (1–7); 1,012 responded at both points (366 in reviewed-log, 351 in open-door, and 295 in no-practice teams). Twelve-month retention came from HR records.

3. Findings

Reviewed-log newcomers recorded 1,266 items, a mean of 7.4 each. Of these, 797 (63%) were explained, 114 (9%) led to a change, 89 (7%) to a trial of an alternative, and 266 (21%) received no recorded response within four weeks. Newcomers rated the explanation they received as satisfactory for 71% of explained items.

At six months, newcomers rated how far their perspective was valued at 5.3/7 in reviewed-log teams, 4.5/7 in open-door teams (an 18% gap), and 4.3/7 in no-practice teams (a 23% gap). Among reviewed-log newcomers, the rating was 5.2/7 for the 93 with no item that led to a change and 5.4/7 for the 78 with at least one. The 31 reviewed-log newcomers with three or more unanswered items rated it 4.4/7. At twelve months, the three groups rated it 5.2/7, 4.5/7, and 4.4/7.

In reviewed-log teams, every credited change arose from a logged item. Practice changes credited to a newcomer's observation within six months came to 0.67 per newcomer in reviewed-log teams, 0.54 in open-door teams (a 24% gap), and 0.52 in no-practice teams (a 29% gap).

Team leads in reviewed-log teams logged 3.4 hours per newcomer over the first four months.

At three months, existing team members rated feeling second-guessed at 3.9/7 in reviewed-log teams, 3.2/7 in open-door teams, and 3.1/7 in no-practice teams. At twelve months the figures were 3.0/7, 3.1/7, and 3.0/7.

Twelve-month retention was 89% in reviewed-log teams, 84% in open-door teams, and 83% in no-practice teams.

4. Discussion

The usual way to justify asking newcomers what they notice is that the team will learn something, and it did, though less than the number of items might suggest. Reviewed-log teams changed somewhat more practices on newcomers' prompting than other teams, but most of what newcomers raised was explained rather than changed.

The quieter result is that the explanations seem to have been enough. Newcomers none of whose items had led to a change felt nearly as valued as those who had changed something. What did not seem to be enough was silence: newcomers with several unanswered items rated themselves about where open-door newcomers did. A newcomer, it appears, does not need the team to agree with what they noticed. They need the team to answer it.

The open door, in this light, offered permission without an answer. It told newcomers they could speak but did not commit anyone to reply, and its results were close to those of having no practice at all.

The answers cost something. Leads spent more than three hours per newcomer, and for the first few months existing members felt their ways of working were being questioned, which they were. Those members gave the time and tolerated the questions; the newcomers, and later the team's own practices, received most of the return. By twelve months the second-guessing ratings had settled back to the level of the other groups.

5. Limitations and Future Directions

Teams chose their own onboarding practice, and leads willing to review a log with each newcomer may differ in other ways that shape how valued newcomers feel. Newcomers in reviewed-log teams were asked to write things down, and writing may itself have shaped their ratings. Change logs depended on teams crediting the person who raised an issue, which some may have done more readily when a log existed. The subgroup with three or more unanswered items is small and was not planned. Retention differences were small and may not reflect the practice. A follow-up will offer the reviewed log to a randomly selected half of teams in participating organizations.

Editorial Note

This report underwent CfAHC's Rapid Review Protocol, including AI-assisted literature cross-checking and a two-reviewer human sign-off.