Prepared for: Ken Lovell · Date: 2026-05-20 · Source artifacts: 5 concepts + 2 finals + HTML exploration pages from Projects/morning-briefing/projects/kl-photography-logo/
1. Critique of existing concepts
16px
32px
64px
128px
Concept 1 — Interlocking Angles
Two separate verticals (x=40, x=120), K's lower diagonal connects to L's baseline. Five strokes.
Favicon: Fails. Two close verticals merge into a blob at 16px.
Embroidery: Marginal. Thread piles up at the K-diagonal/L-vertical junction. Separate verticals need 3mm+ spacing.
Distinctiveness: Low. Two letters next to each other — no design idea, no moment of recognition.
Strengths: Unambiguous letterform reading.
Weaknesses: Forgettable. The connecting diagonal feels incidental. Requires width to breathe — no compact mark version.
16px
32px
64px
128px
Concept 2 — Shared Vertical (WINNER)
K and L share one vertical stroke at center. K diagonals extend left; L horizontal extends right from baseline. Four total strokes.
Favicon: Strong. Reduces to a recognizable asymmetric angular glyph at 16px. The ">|_" shape is identifiable.
Embroidery: Good. Four satin-stitchable strokes, ~2,800 stitches at 3". The mid-point junction (diagonals meeting vertical) is the only density concern — manageable at 55-60 degree angles.
Distinctiveness: High. The shared-vertical is a genuine design idea — "these two letters are one thing." The leftward K energy balanced by the rightward L foot creates memorable asymmetry.
Strengths: Most compact concept. Works as both "KL" initials and abstract angular mark. Stroke-based = inherently scalable. Production-friendly.
Weaknesses: Three-way junction at center creates a visual "knot" at certain stroke widths. The L is implicit — someone unfamiliar might miss it without the horizontal foot cue.
16px
32px
64px
128px
Concept 3 — Side by Side, Heavy Weight
Filled polygon K and L as separate shapes. 240x200 viewport.
Favicon: Fails. Gap between K and L vanishes at 16px → dark rectangle with notches.
Embroidery: Poor. Fill stitches, acute K-diagonal polygon tips = thread bunching. Est. 8,000-10,000 stitches at 3" — too heavy.
Distinctiveness: Medium. Bold and architectural, but reads as a typeface sample, not a mark.
Strengths: Gravitas at large scale — signage, wall art.
Weaknesses: One-trick pony. Only works big. Can't scale down. Can't watermark (too heavy). No unifying design idea.
16px
32px
64px
128px
Concept 4 — Nested
K dominates; L nested in lower-right with shorter vertical (starts y=60 vs K's y=20).
Favicon: Poor. Size hierarchy vanishes at 16px. L vertical and K's lower diagonal run parallel → merge.
Embroidery: Challenging. Parallel strokes at ~2mm separation at 3" — below comfortable minimum.
Distinctiveness: Medium-high. Clever nesting, but L feels subordinate. Reads as "K with an L Easter egg."
Weaknesses: Production killer. L disappears at small sizes. Not a balanced KL monogram.
16px
32px
64px
128px
Concept 5 — Abstract Angular
K as single continuous filled polygon, L as separate aligned polygon.
Favicon: Marginal. K polygon holds up, but the K-L gap problem returns at 16px.
Embroidery: Problematic. K polygon acute-angle tapers = inconsistent stitching.
Distinctiveness: Medium. Polished but no unifying idea. Custom typeface treatment, not a monogram concept.
Weaknesses: Two disconnected shapes. Gap vulnerability persists across all sizes/media.
kl_logo_final_navy.svg
kl_logo_final_white.svg (on light bg)
Final lockups (chosen from Concept 2 family)
Concept 2 mark + horizontal rule + "KEN LOVELL" in graduated caps (large K/L, small EN/OVELL) + "PHOTOGRAPHY" subtitle at reduced opacity.
Strengths: Elegant, editorial lockup. Graduated-caps treatment echoes the mark's hierarchy. "PHOTOGRAPHY" is well-positioned as optional descriptor.
Weaknesses: Full lockup too complex for small embroidery (0.6px rule is un-embroiderable, 9pt text below 3mm min). "PHOTOGRAPHY" must go for universal use. Arial/Helvetica is a non-decision — fine for now but worth revisiting.
---
2. Review panel — four independent voices
PERSONA A — Senior Creative Director (Pentagram-tier)
You've got one good idea in this batch, and you already found it — Concept 2. Everything else is a variant of "put two letters next to each other."
What Concept 2 gets right: It has a design idea. The shared vertical says "these two letters are one thing." That's what makes a mark ownable. This specific geometry — the leftward chevron energy, the rightward foot — is yours.
Concerns with current execution:
1. The junction problem. Three-way intersection at center. At stroke-width 7, that's a dark clot. Needs optical correction — slightly offset the diagonal meeting point so they don't converge at a single pixel.
2. Aspect ratio isn't locked. The mark appears in a 200x200 viewport in concepts but 260x270 in finals. Define the standalone mark's bounding box before putting words under it.
3. The L horizontal feels timid. K diagonals span the full left half. L foot extends about half that to the right. Mark feels like it's falling leftward. Extend the L foot or shorten K diagonals slightly.
4. Drop "Photography" and never look back. For universal use, it's dead weight. "Photography" becomes a swappable descriptor, not part of the mark system.
On the others: Concept 1 is a non-idea. Concept 3 is a typeface choice. Concept 4 is hierarchically broken (one initial looks subordinate). Concept 5 is a cleaner Concept 3 but still two disconnected shapes.
2. Mark + name (header, business card, letterhead, email sig)
3. Mark + name + descriptor (photography, future contexts)
Only Concept 2 supports all three because the mark is complete on its own. Concepts 1, 3, 4, 5 feel incomplete without text — they're illustrations of letters, not standalone symbols.
10-year test: Concept 2 is geometric and timeless — could have been designed in 1965 or 2025. Stroke-based construction means it can be redrawn at any weight without changing DNA.
Concerns:
Arial/Helvetica is a non-decision. Budget a real type selection round — geometric sans-serifs (Futura, Avenir, Montserrat) echo the mark's DNA.
The graduated-caps treatment is clever but fragile — breaks in email clients, CMS fields, embroidery. Need a flat-text fallback.
Design the descriptor slot to accept anything: "Photography," "Design," nothing. The double-rule lockup (type study variant B) handles this well.
Formalize the navy (#1B365D) as the brand color with Pantone, CMYK, RGB, and thread number specs.
Verdict: Concept 2, built into a proper system with three modes, a real typeface, and a defined color palette.
---
PERSONA C — Embroidery & Production Specialist
Production rules designers ignore:
Min satin stitch width: 1.5mm
Min gap between parallel lines: 2mm
Max stitch density for 3" chest mark: ~7,000, ideally under 5,000
Concept 2: Best for production. Four satin-stitchable strokes. K diagonals at 55-60° to vertical — well above danger zone. L foot is clean 90°. I can digitize this cleanly. ~2,800 stitches — light and comfortable on any fabric.
Concept 3: No. Fill stitching, acute tips, 8,000-10,000 stitches. Shirt will be stiff.
Concept 4: Parallel strokes at ~2mm = will merge on pique polo. Too risky.
Concept 5: Same fill-stitch problems as Concept 3.
Production recommendations for Concept 2:
Add 0.5mm radius at junction convergence in stitch file to prevent thread stacking
Column/satin stitch throughout (not fill)
Pull compensation 0.3mm on diagonals
Mark only for anything under 4". Full lockup only at 5+" (jacket back)
Hat embroidery: 2-2.5" center-cap, mark only, no text
Thread colors: Isacord 3732 (Slate) or 3743 (Harbor) for #1B365D navy. 0015 (White) for reverse on dark fabric.
Verdict: Concept 2, mark-only for embroidery. Get me outlined strokes (not live strokes) for digitizing.
---
PERSONA D — Mobile/UX Designer (Apple HIG-era)
Testing against the "essential shape" test: at 16x16, can I identify this from a grid of 30 others?
Concept 1: Landscape proportions in square container. Five subpixel lines at 16px. Reject.
Concept 2: Near-square proportion sits naturally in rounded rect. Asymmetry is the key feature at small sizes — most letter-based icons are symmetrical and blend together. This doesn't. At 16px: ~1px vertical, ~4px diagonals left, ~3px foot right. Identifiable.
Concept 3: Too wide. Gap = 0-1px at 16px. Reject.
Concept 4: L vanishes at 16px. You'd just see a K. Reject.
Concept 5: Two filled shapes with 1px gap = one blurry shape. Reject.
UX specifics for Concept 2:
1. Convert stroked lines to filled/outlined paths for all raster exports (strokes render unpredictably at small sizes)
2. Optically center the mark in square canvas — visual center-of-mass is left of geometric center due to K diagonals
3. App icon: navy (#1B365D) background, white mark (not the reverse — white bg looks like a document icon)
4. Favicon: create size-specific variant with heavier strokes at 16px (1.5-2px vs proportional ~1px)
5. Social avatar: mark only, navy bg, 20% padding — graduated-caps name doesn't survive Instagram's 110px circle
Verdict: Concept 2 is the only viable option for digital. Convert to outlined paths. Size-specific variants at 16/32/48/180px. Navy bg, white mark.
---
3. Recommended direction
Winner: Concept 2 — Shared Vertical, refined.
All four reviewers independently selected Concept 2. It's the only concept with a genuine design idea (shared vertical), the only one that survives the favicon test, the only one that embroiders cleanly, and the only one that works as a standalone mark without text. Refinements needed: fix center junction density, balance L foot length, convert to outlined paths, create size-specific digital variants. Build as three modes (mark-only / mark+name / mark+name+descriptor) with "Photography" as swappable, not permanent.
---
4. Production file plan (38 files across 11 categories)
**38 files total from one master mark:**
### Masters (5 files)
1. `kl-mark-master.svg` — Navy #1B365D, outlined strokes, 200x200 viewBox
2. `kl-mark-master-white.svg` — White reverse
3. `kl-mark-master-black.svg` — Mono-black
4. `kl-lockup-horizontal.svg` — Mark + "KEN LOVELL" side-by-side (~500x120)
5. `kl-lockup-stacked.svg` — Mark above name, sans Photography (~260x230)
### Favicon & Web Icons (5 files)
6. `favicon.ico` — 16/32/48 multi-res, white on navy, size-specific stroke weights
7. `favicon-32.png` — 32x32
8. `favicon-16.png` — 16x16
9. `apple-touch-icon.png` — 180x180, white on navy
10. `safari-pinned-tab.svg` — Single-color black
### App Icons (3 files)
11. `app-icon-1024.png` — White mark on navy, optically centered
12. `app-icon-512.png` — 512x512
13. `app-icon-192.png` — Android PWA manifest
### Social & Avatar (3 files)
14. `avatar-1024.png` — White on navy, 20% padding
15. `avatar-512.png` — LinkedIn, GitHub, etc.
16. `avatar-200.png` — Small-platform fallback
### Web Header & Email (6 files)
17. `kl-header-navy.svg` — Stacked lockup, ~300x80
18. `kl-header-navy@2x.png` — 600x160 retina
19. `kl-header-white.svg` — Dark-mode header
20. `kl-header-white@2x.png` — 600x160 retina dark
21. `kl-email-sig.png` — 200x55, navy, Outlook/Gmail optimized
22. `kl-email-sig-dark.png` — White for dark-mode clients
### Photography Watermark (3 files)
23. `kl-watermark-white.png` — 400x400, 50% opacity, transparent
24. `kl-watermark-black.png` — For light-subject photos
25. `kl-watermark-lockup-white.png` — 600x260, full lockup
### Print & Apparel (4 files)
26. `kl-mark-print-navy.pdf` — Vector, Pantone 289 C
27. `kl-tshirt-navy.png` — 1500x1500 transparent, 300dpi at 5"
28. `kl-tshirt-white.png` — Dark shirt screen-print
29. `kl-tshirt-lockup-navy.png` — 2400x1500 for back-of-shirt/tote
### Embroidery (3 files)
30. `kl-embroidery-mark.svg` — Outlined strokes, junction-optimized
31. `kl-embroidery-mark.dst` — Tajima DST, satin stitch, ~2,800 stitches, 3"x2.7"
32. `kl-embroidery-mark.pes` — Brother/Babylock native
### Art / Merch (3 files)
33. `kl-poster-navy.svg` — Gallery-print source
34. `kl-sticker.png` — 1500x1500, navy on white circle with bleed
35. `kl-mug-wrap.png` — 2700x1100, standard 11oz mug template
### System & Config (3 files)
36. `kl-vcard-photo.jpg` — 512x512, white on navy (Outlook/Apple Contacts)
37. `kl-og-image.png` — 1200x630, navy bg + white mark + name
38. `BRAND.md` — Color specs, spacing rules, usage guidelines
---
5. Integration roadmap
| # | Touchpoint | First Step |
|---|-----------|-----------|
| 5.1 | CP System Header | Drop `kl-header-navy.svg` into `/cp/assets/`, reference in header template. Add favicon to root. |
| 5.2 | PM Sub-pages Favicon | Copy `favicon.ico` to PM webroot, add `` to base template. |
| 5.3 | Morning Brief Email Sig | Embed `kl-email-sig.png` inline in email template footer. |
| 5.7 | Workout Shirts | Give Jacynda `kl-embroidery-mark.svg`. First test: white cotton tee, navy Isacord 3732, left-chest, 3" wide. |
| 5.8 | Document Letterhead | Add `kl-lockup-stacked.svg` to doc template assets, place top-left with 0.5" margins. |
| 5.9 | Theme Accent Color | `--kl-navy: #1B365D` CSS custom property in CP root stylesheet. |
| 5.10 | Social Profiles | Upload `avatar-1024.png` to GitHub, LinkedIn, Twitter/X, Instagram — one sitting, 10 min. |
| 5.11 | Photo Watermark Pipeline | Replace watermark source with `kl-watermark-white.png` in Lightroom preset or ImageMagick script. |
| 5.12 | OpenGraph Tags | Add `` pointing to `kl-og-image.png`. One tag. |
---
6. Next triggers
### T274 — Mark Refinement & Master SVG Production
Refine Concept 2's geometry (junction fix, L-foot balance, optical centering), convert to outlined paths, produce 5 master SVGs + BRAND.md with color specs (Pantone 289 C, CMYK 88-58-10-49, Isacord 3732).
Est. effort: 45-60 min
### T275 — Digital Icon & Favicon Export Pipeline
From T274 masters, produce all favicon/app-icon/avatar variants with size-specific stroke weights and optical centering. Files #6-16. Automatable via rsvg-convert + png-to-ico script.
Deploy mark across live systems: CP header, all favicons, email sig, letterhead, social profiles, theme color, OG tags. Checklist with before/after verification.
Depends on: T275 + T276 | Est. effort: 60-90 min
### Execution Order
```
T274 (masters) ──┬──> T275 (icons) ──┐
├──> T276 (web/print) ──┼──> T278 (integration)
└──> T277 (embroidery) ──┘
```
Total: 3-4.5 hours from concept SVGs to mark deployed everywhere.
---
I wasn't able to write this to file due to permission restrictions — would you like to approve the write so I can save it as `kl_mark_strategy.md`, or is this inline delivery sufficient?