Request for Review | Exceptional Promise | Product Designer (Design Systems Specialist)

1

Hi Everyone,

I’m preparing an Exceptional Promise application as a Product Designer specialising in Design Systems and would appreciate feedback on my MC + OC1 + OC3 evidence.

Background / Personal Statement

My specialism is quite niche - large scale Design Systems across multi platform, multi brand design systems across financial services. My background combines the mix of visual design and business, and I’ve progressed fairly quickly into increasingly specialised roles.

MC1 – Major financial-services rebrand [Company A]

  • P1. Newspaper article: Establishes the scale and significance of the rebrand following the acquisition of a live product led platform.
  • P2. Scope diagram: Shows the breadth of my responsibility across the transition.
  • P3. [Reference] Managing Director + (jira tickets etc if needed): Confirms my personal ownership, contribution and increasing responsibility.

MC2 – Market value / specialist expertise

  • P1. Company A Payslip + salary benchmark (glassdoor): Shows my permanent salary was above the benchmark for comparable roles.
  • P2. Company B Contract + market-rate benchmark (itjobswatch): Shows my subsequent specialist contract was also above the wider market.
  • P3. [Reference] Industry expert who hired me for Company B (Separate person from the letter of recommendation). Supports the scarcity of specialism and explains why my directly comparable experience was relevant to the role + LinkedIn recruitment screenshot for (500+ interactions. Not sure if acceptable as supplementary evidence)

OC1-A – Innovation [Company A]

  • P1 – Design artefacts: Shows the existing problem and the new approach I developed.
  • P2 – Implementation records: Shows how the approach was put into practice while live product delivery continued.
  • P3 – (?) Outcome evidence / [Reference] SLT employee / [Reference] Industry Expert: Supports my ownership and the case that the approach was genuinely novel rather than routine work.

OC1-B – Innovation [Company B]

  • P1 – Problem / workflow diagram: Shows how multiple product teams were independently solving similar problems.
  • P2 – Operating-model diagrams + working artefacts: Shows the new approach I developed to improve collaboration and reuse.
  • P3 – (?) Evidence / [Reference] Software Engineer collaborator / [Reference] Industry Expert): Shows the approach being used across teams and its wider organisational relevance.

OC3-A – Significant contribution: governance [Company A]

  • P1 – Internal system / workflow screenshots: Shows the governance infrastructure I introduced.
  • P2 – Process diagrams + implementation evidence: Shows how I adapted the approach to improve adoption and ways of working.
  • P3 – [Reference] SLT Director Engineering: Confirms that I identified the problem, introduced the solution and reduced delivery/consistency risk.

OC3-B – Significant contribution: product-team adoption [Company B]

  • P1 – Before / problem evidence: Shows the inconsistency and organisational problem I was addressing.
  • P2 – Solution + enablement evidence: Shows the solution and working practices I introduced.
  • P3 – [Reference] Senior product designer: Confirming the use of the solution and how it changed their way of working

Recommendation letters

  • Letter 1: Managing Director-level design leader (Company A) who was in my senior leadership chain for ~2 years and knows my progression and work in detail.
  • Letter 2: Very high-profile Design Systems industry leader (Company B) who was also my manager and can speak directly to my specialist expertise and the scarcity of comparable experience.
  • Letter 3, Option A: Senior design leader from (Company A). We never worked together directly, but later developed a mentor–mentee relationship and I interviewed with him for another role.
  • Letter 3, Option B: Well-known Design Systems community organiser who knows me through the industry community, but knows my actual work less well.
    Option B would be harder to secure, so I’m trying to understand whether the additional independence/industry recognition is genuinely worth pursuing.

*

I know I’m weaker in the more conventional Tech Nation areas such as awards, publications, open source and major speaking. I’m hoping the niche nature of Design Systems, the narrative, small talent pool, career progression and strength of my work demonstrate potential.

Unfortunately, I also need to apply relatively soon and this is my only realistic option right now so I’m trying to make the strongest case from the evidence I already have.

Main questions

  1. Does this overall evidence mapping make sense for MC, OC1 and OC3?
  2. For OC1, could a recognised industry expert who doesn’t know me well provide a short statement assessing the approach itself against wider industry practice?
  3. Can OC3 still be strong where the impact is mainly systemic/organisational rather than directly tied to revenue or user growth?
  4. My manager was also a high profile, recognised industry expert, and I was subsequently hired into his team because of the relevance of my specialist experience. Can his corroboration carry meaningful weight for OC1/OC3, or would Tech Nation view it as not independent?
  5. For the third recommendation, should I prioritise deeper knowledge of my work or greater external industry independence?
2

The main structural risk is that both optional criteria describe the same kind of work. The Guide draws a hard line: OC1 asks for innovation (novelty, not impact) while OC3 asks for significant contribution (impact, not innovation), and warns the same evidence used for both may not be enough. Your operating-model and governance work reads as impact and adoption, which sits far more naturally under OC3. For OC1 as an employee the bar is a genuinely new digital field or concept, and process or reuse improvements to an established discipline will struggle to clear it. I would question whether OC1 is your strongest second criterion.

Every reference letter, including ones used as evidence, must come from someone with detailed knowledge of your work over 12 months or more. An industry expert asked to assess the approach in the abstract, without knowing your work, will not meet that, and letters alone cannot establish a criterion anyway. Your former manager is fine as an evidence letter for OC1 or OC3, since an employer letter is explicitly accepted there. A manager only fails to count for Mandatory recognition, where an immediate manager is named as insufficient.

For the third letter, prioritise depth of knowledge over external profile. A well-known name who cannot speak to your actual work in detail fails the same 12-month test and reads as a name lent rather than a colleague vouching for you. Systemic impact works for OC3 without revenue or user numbers, as long as the evidence shows your personal contribution.

1 Like
3

Your evidence mapping is broadly logical, but the main challenge will be making the distinction between MC, OC1 and OC3 very clear. For MC, salary and specialist demand can support recognition, but I would suggest you to avoid making market value the main argument unless the evidence clearly demonstrates that your remuneration is exceptional for your field. I would, therefore, use salary evidence as supporting context rather than making it the central proposition. The rebrand evidence will also need to show recognition of your personal contribution, not just the significance of the company or project.

For OC1, your approach can work if you can clearly demonstrate that the Design Systems solutions were genuinely innovative rather than standard design practice. A recognised industry expert who does not know you well could provide a statement assessing the approach against wider industry practice, but this should support rather than replace evidence of your own ownership and implementation. Your manager’s corroboration can still carry weight if they have detailed first-hand knowledge of your work, even though they are not fully independent.

OC3 does not need to be based solely on revenue or user growth. Systemic and organisational impact can be relevant if you can demonstrate that your work led to meaningful adoption, improved consistency, reduced risk, improved delivery or changed how multiple teams operated. The stronger the measurable evidence of that impact, the better.

There is some potential overlap between your OC1 and OC3 evidence, so it would be better to make OC1 about what was new and why it was innovative, while OC3 should focus on your significant contribution and the resulting organisational impact.

For the third recommendation letter, I would generally prioritise someone with deep, credible knowledge of your work over someone who is more independent but can only make general statements. The strongest letters usually combine the recommender’s standing with detailed, first-hand knowledge of your achievements.

Good luck.

4

@Promising Trust, you are good.

Let’s start with your narrative. For designers now, the endorsing body they qualify through depends on their area of design. Product Designer, the last time I checked, was not listed as an eligible role on Tech Nation guidance. What you have close to that are Experienced UX/UI Designers and Experienced Front-End Developers. But because your role sits between design and engineering, you need to be a bit strategic here. (Product Designer UI/UX) can be a safe alignment point for you. However, the evidence you are presenting will still be checked against your chosen discipline. And to confirm, I have supported product designers UI/UX who got endorsed. So, it largely depends on the narrative and how rightly the evidence align to the guidance vis-a-vis the discipline area.

On your evidence:

MC1 – Major financial-services rebrand [Company A] - A newspaper establishing the scale and significance following the acquisition of a company will not show how you led the growth of a product-led digital technology company, product, or team, except if you are the founder/co-founder of that company. That would mean your oversight responsibilities contributed to the acquisition, and the newspaper is validating that the company was acquired. But as an employee, no. Also, a scope diagram will not show that you did anything within a company that is capable of advancing the sector. A reference letter can validate what you did internally in relation to leading the direction of the company, product, or team, but it is not sufficient without convincing evidence. Jira tickets assigned to you will not clearly show the leadership Tech Nation expects.

MC2 – Market value / specialist expertise The guidance is clear that salary alone is not enough, and from the feedback I have seen over the years, it is safe to say that regardless of how much you earn, salary alone is not enough. A letter from an industry expert on its own is not sufficient. So you have two types of evidence that are not sufficient on their own.

OC1 – Innovation OC1 is about innovation or something entirely new in a new concept. Design artefacts and implementation records will not show that you have innovated a new design concept. OC1 can work for developing an approach that solves a problem, but that approach needs to be considered, acknowledged, and accepted as first of its kind through a patent, sales, or adoption. What do you mean by outcome evidence? Letters are not sufficient, regardless of who writes them, they are required only to validate or reference the correctly aligned evidence.

Problem/workflow diagrams will not show innovation. Operating-model diagrams can be okay, but innovations must be validated by something like a patent, commercial sales, or a relatively strong externally validated evidence Tech Nation can accept. It appears you have a reference letter for every evidence set, this is not strategic. Application wise, you should have at most two to three(My opinion). Preferably, I suggest at most two.

Your OC3 looks similar to your OC1. Also, governance [Company A] does not appear to be a product-led company. Is this a government establishment, or did you have a governance role? OC3-B is descriptive, what evidence are you submitting here as “Before/problem evidence”?

For LOR, you need just three established industry experts who have known you and your work for at least 12 months.

On your questions:

  1. Does this overall evidence mapping make sense for MC, OC1 and OC3?

No. I have stated some of the reasons above.

  1. For OC1, could a recognised industry expert who doesn’t know me well provide a short statement assessing the approach itself against wider industry practice?

A reference letter on its own is not evidence and can only support and validate evidence that aligns with the criterion, regardless of who writes it.

  1. Can OC3 still be strong where the impact is mainly systemic/organisational rather than directly tied to revenue or user growth?

Your OC3 is not currently tied to any growth. Impact is a validating evidence that shows the value of what you did. You first need to clearly show technical contributions to a product-led company first, before talking about the impact of your contributions.

  1. My manager was also a high-profile, recognised industry expert, and I was subsequently hired into his team because of the relevance of my specialist experience. Can his corroboration carry meaningful weight for OC1/OC3, or would Tech Nation view it as not independent?

Tech Nation application is about you, not your manager. So his corroboration will not do so much.

You have done well and it’s a good starting point. But going by recent feedback from Tech Nation, I suggest you give some time and work on strong evidence that rightly aligns with the Tech Nation guidance to improve your chances.

All the best.