Northwind
Kitchenware Co.
This guide defines how Northwind looks, sounds, and communicates — across every customer touchpoint, internal document, and business communication. It is the single source of truth for anyone representing the brand.
Understanding who we are and how we got here is the prerequisite to every design and communication decision that follows.
Our Origin
Northwind Kitchenware was founded in 2009 by Diane Halloran, a product designer who started with one product — a high-quality pour-over coffee kettle, handcrafted in a rented workshop in Bend, Oregon. That kettle caught on with specialty coffee shops not because it was the cheapest or the flashiest, but because it was simply very well made.
That initial impulse — build something honest, something that works — has never changed. From that single kettle, Northwind expanded into a focused line of kitchen appliances and durable housewares across four product lines: Brew, Prep, Cook, and Connected.
Where We Stand
Today Northwind sells through its own DTC channel, Amazon, and roughly 1,200 independent and regional retail accounts. We are a privately held company with a minority growth investment from Cascade Hill Partners, approximately 150 employees, and ~$41.5M in annual revenue (FY2025).
We design every product in-house in Oregon and contract production to carefully chosen partners in Vietnam and China, with final assembly and quality control at our Redmond, Oregon distribution center. We are profitable, thoughtful about growth, and deeply committed to the product quality that built this company.
"For home cooks who want better-than-entry-level quality without premium-brand pricing, Northwind delivers clean, functional kitchen products designed to last — backed by the responsive service that has defined us since day one."
Three commitments define every Northwind product, document, and interaction. When in doubt about any decision — creative, operational, or communicative — return to these pillars.
Function First
Every product and every document should do its job well before it looks good. Form follows function — always. Decoration for its own sake is not Northwind.
Built to Last
Northwind products are made to outlast trends. Our brand materials should reflect that same durability — no gimmicks, no date-stamped trend chasing, no disposable design.
Straightforward Quality
We are honest about what we are. Mid-price, serious quality, responsive service. We do not inflate, exaggerate, or obscure. Our communications should always reflect this directness.
Target Audience
Primary: Home Cook
Ages 28–55 · HHI $60K–$140K · Values quality and design over status brands · Researches before buying · Keeps products a long time · Appreciates transparency and honest product claims.
Secondary: Wholesale Buyer
Independent kitchen store buyers and regional chain category managers · ~1,200 accounts · Want reliable margin, low return rates, and clean brand presentation that fits their store identity.
Northwind has one voice — direct, warm, and grounded in craft. Tone adjusts depending on context: more precise in business documents, warmer in customer communications, more direct in internal ones.
Brand Personality
Tone by Context
✓ Write This Way
✕ Avoid This
The Northwind wordmark is the primary brand identifier. It uses DM Serif Display for the logotype, paired with the descriptor set in Josefin Sans at wide tracking. The wordmark may appear in four approved configurations.
✓ Correct Usage
- Use only the four approved color combinations shown above
- Maintain clear space equal to the cap-height of "N" on all sides
- The wordmark always stacks: logotype → rule → descriptor
- The full wordmark "Northwind Kitchenware Co." appears on all formal documents
- The shortened "Northwind" may be used in running text and email signatures
✕ Never Do This
- Do not stretch, condense, or skew the wordmark
- Do not use the wordmark in colors outside the four approved configurations
- Do not place the wordmark on busy photographic backgrounds without a clear zone
- Do not separate the logotype from the descriptor in formal contexts
- Do not use the wordmark at sizes below 80px wide in digital or 1 inch in print
The Northwind palette draws from the Pacific Northwest landscape and the warmth of a working kitchen. Slate and midnight anchor the brand; copper provides energy and warmth; linen and white give space and legibility.
Color Usage Examples
Northwind uses a three-family type system: DM Serif Display for headlines and brand presence; Josefin Sans for labels, navigation, and structural text; Lora for all body copy and document prose. IBM Plex Mono handles all data, codes, and identifiers.
Type Scale
Sales orders, quotations, and other customer documents represent Northwind to buyers, wholesale accounts, and retail partners. They must be precise, visually consistent, and reflect the quality of the products they describe.
Sales Quotation — Anatomy
Header Block
Slate background. Full wordmark left-aligned. Document type ("SALES QUOTATION") and document number in Josefin Sans uppercase on the right, followed by issued date and expiry. Document numbers use Mono font.
Parties Section
Two-column grid: "Bill To" on the left with customer name, contact, and address; Northwind representative name, title, and email on the right.
Line Items
Product name in Lora with SKU code in IBM Plex Mono below it. Quantity, unit price, and line total right-aligned. Grand total separated by a double rule. All currency to two decimal places.
Footer
Linen background. Payment terms and document conditions left-aligned in italic body font. Northwind website and HQ location right-aligned in Mono.
Document Numbers
Quotations: Q25-XXXXX · Sales Orders: #NW-XXXXXX · Always set in IBM Plex Mono · Never omit or abbreviate.
Internal documents — reports, briefs, operational summaries — are tools, not presentations. They carry a banner identifying them as internal, use the same type system, but prioritize density and clarity over visual weight.
Q2 FY2025 Connected Line Review
The Connected line continues to grow faster than any other segment (+31% YoY) but carries a return rate more than twice the company average. Root-cause analysis of NW- support tickets points to firmware update inconsistencies, primarily on the CN-501 Smart Kettle.
1. Prioritize firmware patch for CN-501 before Q3 holiday pre-orders open. 2. Add in-box setup guide specific to Connected onboarding. 3. Flag return rate threshold in Looker for weekly executive visibility.
Internal Banner
All internal documents open with a midnight-colored banner identifying the company and document classification (INTERNAL, CONFIDENTIAL, or DRAFT). This distinguishes internal work from customer-facing documents at a glance.
Metadata Block
Immediately below the title: Author name and title · Date prepared · Intended audience. All in Josefin Sans, small uppercase. This is mandatory — undated, unattributed internal documents are not acceptable.
Key Facts Grid
For reports and reviews, open with a 2×N grid of the most critical facts in linen-colored key-value cells. Readers should be able to understand the document's subject in 10 seconds.
Section Heads
Use copper-colored, all-caps Josefin Sans headers with a horizontal rule below. Sections should be named for their content, not generic labels ("Situation Summary" not "Background").
Solution design docs describe technical or operational systems — from software architecture to distribution process redesigns. They serve engineers, operations leaders, and occasionally external partners. Clarity and traceability are the primary requirements.
Delivery Architecture
Define the end-to-end firmware update delivery pipeline for Connected line SKUs (CN-501, CN-502, CN-503) to reduce firmware-related returns and support tickets for Q3 FY2025 and beyond.
In scope: OTA delivery mechanism, version control schema, rollback procedures, and customer communication triggers. Out of scope: companion app UI changes (tracked separately under SDD-2025-011). Budget ceiling: $0 infrastructure cost increase; solution must use existing AWS stack.
In Review Pending sign-off from Marcus Tran (COO) and Ben Olsen (VP Product). Target approval: June 30, 2025.
Document ID
All solution design docs carry a sequential identifier: SDD-YYYY-NNN. This ID appears in the header, in version control commit messages, and in any document that references this design.
Required Sections
Every SDD must include: Objective · Scope & Constraints · Technical Design · Dependencies · Testing / Validation Criteria · Status & Approvals. Sections may be expanded but not omitted.
Status Badges
DRAFT IN REVIEW APPROVED SUPERSEDED
Version Control
Version numbers follow semantic format: 0.X for drafts under review, 1.0 on first approval, X.0 for major revisions. Change log is appended to the document, not overwritten.
Email is the most frequent touchpoint between Northwind and the world. Consistent signatures, clear subject lines, and disciplined formatting reflect the brand in every message.
Email Signature
Signature Rules
Required Elements
Full name · Title · Work email · Phone (optional for internal) · Website · Company name with city and tagline.
No Graphics
Email signatures use text only. No embedded images, social media icons, or promotional banners. These break in many email clients and look unprofessional in plain-text threads.
No Confidentiality Disclaimers
Legal boilerplate disclaimers appended automatically to every email are not Northwind style. If an email is confidential, say so in the body of the email itself.
Subject Line Format
Body Format
Lead with the Point
State what you need or what's changed in the first sentence. Context and background follow. Never bury the ask in paragraph three.
Short Paragraphs
No paragraph should exceed four lines. White space is not waste — it aids reading. Use a line break between paragraphs.
One Ask Per Email
If you need three things, and they're unrelated, send three emails. If they're related, number them clearly: "I need three things from you: 1. … 2. … 3. …"
Memos are used for formal internal communication — policy announcements, operational decisions, cross-functional updates that need a record. They are more structured than email and should be treated as official documentation.
Holiday pre-orders open July 14. To ensure on-time fulfillment for our wholesale accounts and DTC orders, we are implementing the following cut-off dates for the Redmond DC.
All inventory transfers from contract manufacturing partners must arrive at Redmond by August 15. Any SKUs not cleared through final QC by August 20 will not be available for the initial holiday window.
Questions should go to Aisha Bello (aisha@northwindkitchenware.com) in Supply Chain. A detailed timeline with per-SKU status will circulate next week.
Memo Structure Rules
Header Block
Linen background with a bottom border in Slate. Northwind wordmark at top. Four mandatory fields: To, From (with title), Date (written out in full — never MM/DD/YY), and Re (subject line, no period at the end).
Subject Repetition
The Re: subject repeats as a visible heading at the top of the body. This is intentional — readers should understand the memo's topic before reading a word of body text.
Body Length
Memos should not exceed one printed page (approximately 300–400 words) unless the subject genuinely requires more. If your memo runs long, consider whether it should be a brief report instead.
Signature Close
End with author name (italicized) and full title. No "Sincerely" or "Best regards" — memos are formal documents, not letters. No sign-off phrase is cleaner and more professional.
Distribution
If the memo is sent to a named list rather than "All Employees," append a CC or Distribution List at the bottom of the memo, not in the header To: field.
Consistent data, identifiers, and contacts used across all Northwind documents. Use these exactly as written.