• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer

Satisfice, Inc.

Software Testing for Serious People

Rapid Software Testing A Context-Driven Methodology
  • Home
  • About
    • Privacy Policy
  • Methodology
    • Exploratory Testing
    • Reasons to Repeat Tests
  • Consulting
  • Classes
    • James Bach’s Testing Challenge
    • Testimonials
    • RST Courses Offered
    • Testers and Automation: Avoiding the Traps
    • Rapid Software Testing Explored
    • Rapid Software Testing Applied
    • Rapid Software Testing Managed
    • Rapid Software Testing Coached
    • Rapid Software Testing Focused: Risk
    • Rapid Software Testing Focused: Strategy
  • Schedule
  • Blog
  • Contact
  • Resources
    • Downloads
    • Bibliography: Exploratory Process
    • Bibliography: Risk Analysis
    • Bibliography: Coaching
    • Bibliography: Usability
    • Bibliography: My Stuff From IEEE Computer and IEEE Software Magazines
    • Bibliography: The Sociology of Harry Collins

Obvious/Oblivious

Published: November 16, 2003 by James Bach 3 Comments

(Revised: 1/2015)

As a process guy, I often hear the term “common sense”. It’s a strange term. Like “luck” it’s a concept that generally brings an end to inquiry, because it’s a reference to magic. “That’s just common sense” seems to be a signal that “I haven’t thought about that, and I’m not prepared to talk about it, either.”

Same with the word “obvious”, sometimes. When you ask a technical question about a product and a developer says that the answer is obvious, you can generally count on that to mean that he hasn’t discussed the matter with anyone. Not discussing it, the team is likely to be oblivious to risks associated with it, if there are any.

It is the tester’s duty to keep an eye on things that seem unimportant, yet might be important after all.

Just because something about a product is obvious to one person, doesn’t mean it’s obvious in the same way to everyone. It may be especially non-obvious to a user.

The obvious leads to the oblivious, and that makes me nervious.

Filed Under: Heuristics, Language, Process Dynamics, Risk Analysis

Reader Interactions

Comments

  1. Dale Emery says

    16 November 2003 at 6:06 am

    Here’s how I translate “obvious”: Not obvious, and very likely not true.

    And welcome to the blogosphere!

    Reply
  2. Adrian Howard says

    2 December 2003 at 9:34 am

    Another translation of “obvious” is “I can’t articulate that”.

    One of the things I find hardest is extracting why one particular solution is “obvious” to an expert practitioner. The “obvious” solution is correct, it’s just that the process that led to it is no longer open to introspection (if it ever was) in the experts head.

    (and gosh darn it I really hate “common sense” too 😉

    Reply
  3. ytf says

    19 December 2003 at 2:39 pm

    Along with “obvious” and “common sense”, we need to mention the utterance “it goes without saying”–which phrase I have always enjoyed because it *makes explicit* the silence, and then claims to end it.

    Even then, the potential cognitive slip is, of course, that other things remain which might have also gone without saying.

    Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Primary Sidebar

Search

Categories

  • About Me (17)
  • Agile Methodology (14)
  • AI and Testing (4)
  • Automation (20)
  • Bug Investigation and Reporting (9)
  • Buggy Products (24)
  • Certification (10)
  • Context-Driven Testing (44)
  • Critique (46)
  • Ethics (22)
  • Exploratory Testing (34)
  • FAQ (5)
  • For Newbies (25)
  • Heuristics (28)
  • Important! (20)
  • Language (35)
  • Management (20)
  • Metrics (3)
  • Process Dynamics (27)
  • Quality (8)
  • Rapid Software Testing Methodology (23)
  • Risk Analysis (13)
  • RST (5)
  • Scientific Method (3)
  • Skills (30)
  • Test Coverage (8)
  • Test Documentation (8)
  • Test Oracles (5)
  • Test Reporting (11)
  • Test Strategy (26)
  • Testability (4)
  • Testing Culture (96)
  • Testing vs. Checking (18)
  • Uncategorized (12)
  • Working with Non-Testers (7)

Blog Archives

Footer

  • About James Bach
  • Satisfice Blog
  • Bibliography: Bach on IEEE
  • Contact James
  • Consulting
  • Privacy Policy
  • RST Courses
  • RST Explored
  • RST Applied
  • RST Managed
  • RST Coached
  • RST Focused: Risk
  • RST Focused: Strategy
  • RST Methodology
  • Exploratory Testing
  • Testing Training
  • Resources
  • Bibliography: Exploratory
  • Bibliography: Risk Analysis
  • Bibliography: Coaching
  • Bibliography: Usability
  • Bibliography: The Sociology of Harry Collins
  • Schedule
  • Upcoming Public Classes
  • Upcoming Online Classes
  • Public Events
  • Tester MeetUps

Copyright © 2025 · News Pro on Genesis Framework · WordPress · Log in