Collection
Keep the meaning intact when data moves
Make joins, identifiers, updates and completion checks preserve the business meaning of the records being moved.
10 elements · Explore in any order.
3 checklists · 4 protocols · 1 question · 2 templates
10 elements
Name what one row means before joining two tables
The join may be working perfectly on the wrong relationship.
Read the idea ProtocolReconcile what is missing and what should never have arrived
Everything expected can be present while the result is still wrong.
Read the idea ChecklistGive omitted, null and blank different test cases
An empty-looking cell can carry a very active instruction.
Read the idea ProtocolKeep the unit attached when moving the number
The number 500 is impressively precise about almost nothing on its own.
Read the idea TemplateMake every selected record end in an explicit status bucket
A total should account for the awkward records too.
Read the idea ProtocolImport identifiers as text before a spreadsheet can reinterpret them
A customer code is a name wearing digits, not necessarily a number.
Read the idea QuestionChoose the clock before assigning an event to a period
Arrived today and happened today are different statements.
Read the idea ProtocolJoin historical work to the version that was valid then
Today's organization chart did not manage last year's sale.
Read the idea TemplateMatch the identifier together with its issuing namespace
Record 123 in one system has not introduced itself to record 123 in another.
Read the idea ChecklistFollow an accepted job to its actual completion state
Accepted is a place in the queue, not a certificate of completion.
Read the idea