Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Having personally worked in both healthcare and construction (sometimes even healthcare construction), I disagree.

Roles are not nearly as defined as you suggest. Take construction: there will always be conflicts between sub-domains. If there’s a clash between disciplines there’s nothing more frustrating than two sub-contractors who point to each other as the one who must “own” the problem to fix it. Same thing in healthcare. A surgeon who won’t do a task because they believe it’s beneath them is not benefiting the patient.

I don’t think most missions are capable of having clearly defined roles like you suggest. There will always be jobs that fall in the gray area and that’s why almost every job I’ve had included a “and other duties as assigned.”

I agree that perspective is important, but that’s talking about prioritization not shirking duties. I also understand burn out is a real risk, but I don’t think the right mitigation is taking a "that's not my job" perspective; I'd much rather see someone work with their supervisor to say, "here's where that falls in my current priorities". "It's not my job" tends to results in un-productive finger pointing or venting as opposed to actually aligning one's work with what's important to the shared mission.

I want to work with problem solvers not people who identify with strictly defined roles.



Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: