#Not_My_Type
Projects I turn down and why. Expensive lessons from discovery calls with 17 stakeholders, redesigns that hide pricing problems, and other red flags.
The founder sent it the night before our first call. “Background reading,” he said. “So we’re not starting from zero.” It was a UX design competitive analysis. Thorough doesn’t cover it. Fourteen competitors mapped across 23 dimensions. Feature matrices with colour-coded cells. Pricing tables. Screenshots of onboarding flows annotated with commentary. A section called “UX…
The submission went in on a Tuesday. Formal prose. Technical subject. Revised three times. The kind of writing that takes longer than it looks. The editor came back Thursday. The ai checker said 100%. Policy required disclosure or rejection. I wrote every word of it… You submit something to a publication. The editor runs it…
The research is done. Six weeks. Twelve user interviews. A 47-slide synthesis deck with themes color-coded in four shades of blue. The researcher presents to the cross-functional team on a Thursday afternoon. Everyone nods. Someone says “this is really valuable.” Someone else says they’d love to dig into the data more when they have time.…
You know how this goes. Three weeks on the portfolio. Rewrote the case study twice. Rebuilt the layout because something felt off at midnight on a Wednesday. Sent it to two designer friends who said it was strong. Found the right contact on LinkedIn, personalized the message, attached the link. Three days later: automated rejection.…
The wireframes looked perfect. Clean navigation. Clear hierarchy. Logical flow. Three stakeholders approved everything in 45 minutes. “This is exactly what we need.” PM scheduled development to start Monday. Then the designer added real content. Product names weren’t the placeholder “Product Name” shown in wireframes. They were 43 characters with special symbols and line breaks:…









