First: I totally agree that one needs to know the frequency or distribution of key data characteristics.
Second, re: "you could include enough columns (such as IsEmployee) to flag the relationships any person has with the organization."
I've used a different approach: Model the relationship as a data column, named perhaps: person_type_cd [Person-Type Code]. I also set up a set of valid values (My DBA reference-implementation calls this a domain table). In your example, I might choose:
CU - customer
EM - employee
VN - vendor
BD - member of the board.
One immediate benefit: I can index on person_type_cd to resolve the implementation issue you identify with indexing multiple flag columns.
Another benefit: If (when) the business model grows or changes, I can add additional person_type_cd values without redesigning the database.
Another benefit: If (when) the data characteristics change (for instance, we acquire a company with 1,000 employees, 300 customers and 10 vendors) the database design is probably not impacted by this shift in the distribution of the data characteristics.