7. Culture & External Factors

Part of the Software Project Maturity Assessment — spec version 0.3.0.

7.1 Working Conditions

Why it matters: Tooling friction, noisy environments, and poor ergonomics are a constant tax on attention; engineers who fight their environment every day have less left for the actual problem.

What good looks like: Engineers have the hardware, software licenses, and workspace (physical or remote) they need without a fight, and requests to fix friction are resolved in days, not quarters.

Questions to ask: - What's the most recent piece of hardware or tooling you requested, and how long did it take to get it? - Is there anything you work around every day because getting it fixed properly isn't worth the effort of asking? - How would you describe your build/test feedback loop on your actual machine — is local iteration fast enough to stay in flow? - If you needed a second monitor, more RAM, or a paid tool license tomorrow, what's the process?

Red flags: engineers self-fund tools or hardware because expensing them is too much friction; long-standing environment complaints nobody owns; "just deal with it" is the answer to raised friction.

7.2 Remote Work / Hybrid Efficiency

Why it matters: Distributed and hybrid teams either build deliberate habits for asynchronous work and inclusive meetings, or they quietly become two-tier organizations where whoever is in the room (physical or first-to-type) has more influence and better information.

What good looks like: Decisions and important context are captured in writing by default, meetings are run so remote participants have equal voice, and cross-timezone work doesn't consistently land on the same people's off-hours.

Questions to ask: - Can you name a decision that was made in a hallway or in-office conversation and only reached remote teammates late, or not at all? - When a meeting has both remote and in-office participants, does it actually work for the remote side, or are they observers? - What's written down asynchronously versus what only exists as tribal knowledge from a conversation you had to be present for? - Across time zones, whose working hours get inconvenienced by default?

Red flags: "you had to be there" is a recurring phrase; async updates are theater while the real decisions happen in a side channel or in-person; one timezone consistently absorbs the inconvenient meeting times.

7.3 HR & Recruiting Alignment

Why it matters: Engineering and people operations that don't talk to each other produce mismatched hiring bars, roles that don't match the work, and attrition nobody sees coming until it's an exit interview.

What good looks like: Engineering has real input into hiring bar and role definitions, people operations understands what's happening on the ground (workload, morale, attrition risk) before it becomes a crisis, and the two functions coordinate rather than operate in silos.

Questions to ask: - When was the last time engineering leadership and HR/people ops talked about team health, and what came out of it? - Who sets the technical hiring bar — is it engineering, or does HR run the process largely independently? - If someone on the team were flight-risk right now, would people ops know before they resigned? - How closely does the actual job match what was advertised or promised at hiring time? - Are interviews structured around consistent, role-relevant criteria, and do interviewers have guidance to assess candidates consistently and fairly?

Red flags: engineers learn about org changes affecting them from HR announcements rather than any prior conversation; hiring bar is set unilaterally by whichever function runs the process; exit interviews surface the same complaint repeatedly with no visible change.

7.4 Continuous Learning & Growth

Why it matters: A team that stops learning stagnates technically and loses its best people to teams that don't; growth has to be a structural investment (time, budget, paths) rather than something squeezed into whatever's left of a person's own time.

What good looks like: There's real budget and protected time for learning, growth paths exist and are understood (not just an org chart with one ladder), and knowledge-sharing happens as a habit, not an occasional event.

Questions to ask: - When did you last use a training budget, attend a conference, or take a course on work time — and was it easy to get approved? - Do you know what it would take to get promoted or move to a different track, or is that opaque? - How can team members access coaching or mentoring, and how are those relationships helping them develop skills or pursue career goals? - Is there a recurring guild, brown-bag, or knowledge-sharing session, and do people actually show up? - What's something you learned recently that you had to pursue entirely on your own time and dime?

Red flags: training budget exists on paper but is never actually spent or approved; growth paths are undocumented and depend on informal advocacy; knowledge-sharing sessions were tried once and quietly died from lack of attendance.

7.5 Team Health & Culture

Why it matters: Morale, psychological safety, and wellbeing aren't soft add-ons — they're leading indicators; teams that feel unsafe to speak up or are quietly burning out will show the damage in quality and attrition long before it shows up in a survey.

What good looks like: People raise disagreement, mistakes, and bad news without fear of punishment, workload and burnout are actively monitored rather than assumed fine, and DEI is practiced as equitable access to opportunity, mentorship, and fair treatment — not just a stated value with no visible outcome.

Questions to ask: - When did someone last disagree with a tech lead's or manager's decision in the open, and what happened afterward? - How would the team find out if a teammate was quietly burning out — is anyone watching for it, or does it surface only at resignation? - Can you describe a mistake that was owned openly and discussed without blame, versus one that got swept under the rug? - Do people from different backgrounds get equal access to high-visibility work, mentorship, and fair feedback here? - Is there a way to raise a concern about team culture or conduct that doesn't require going through the person you have the concern about?

Red flags: disagreement with leadership is rare or happens only privately, never in open forums; burnout is discovered at resignation, not before; DEI exists on paper with no accountability or visible outcomes; concerns can only be raised through the person the concern is about.

7.6 Other

Anything important to this category that the items above did not cover. Record it here with an importance and state rating like any other item.