Denver Nuggets Sign Ryan Nembhard to a Two-Way Contract, Waive KJ Simpson

Twenty-three assists in a single game. Ryan Nembhard did that against the Chicago Bulls last season. In the same season, he scored 28 points — a career high — against the Denver Nuggets themselves.

Put those two facts side by side and the picture becomes clear. Denver did not sign a stranger. They signed a player who had already hurt them twice in one season.

Before anyone else could name it, I had already seen the frame. This is a small move against the salary sheet, but a loud signal about how the Nuggets front office views its bench.

One name, two brothers, and a common mistake

Before the tactical section, one point about names needs to be settled. Ryan Nembhard is the younger brother of Andrew Nembhard, the guard currently playing for the Indiana Pacers. They play the same position, both came out of the Gonzaga system, and both lean toward a playmaking style. Media outlets merging the two names is an error I have seen repeated in short-form reporting. Get a name wrong once, and I build my own dictionary. Here the distinction is not only about pronunciation — it is about skill profile.

Andrew is a guard who can play both ends at playoff rotation level. Ryan has not proven that yet. Confusing the two means confusing two entirely different levels of readiness.

Context: Denver buys depth with the smallest currency available

Denver signed Ryan Nembhard to a two-way contract and simultaneously requested waivers on KJ Simpson. Technically, a two-way deal carries a fixed salary below the standard minimum, and under standard NBA treatment it does not occupy a meaningful cap charge. It is a tool designed for exactly this situation.

Waiving Simpson is the more telling part. Denver had invested development time in him, then decided to stop. The front office is willing to pivot quickly at the backup guard spot. For a team inside its contention window, constantly testing and discarding the third and fourth guards is how you save money without losing competitiveness.

Nembhard is 23 and went undrafted. Last season he appeared in 60 games and started 27 for Dallas. Those 27 starts matter more than they appear. Most two-way signings enter the league with almost no real rotation experience. Nembhard already has it. He has had to face opposing starting units, read NBA-level defenses, and carry responsibility when his team lost.

Jamal Murray is Denver's primary lead guard. The team's need sits behind Murray: someone who can handle the ball, organize the offense, and keep the system from collapsing during Murray's rest minutes. Nembhard was signed into exactly that slot.

This transaction needs to be placed in its proper league context. Denver belongs to the contender tier in the West, but they are not a team with significant financial room. A team near the apron cannot buy depth with cash. It has to buy it with two-way slots, with the draft, with small bets. This move says far more about Denver's financial limits than about Nembhard's caliber.

Data analysis: a passer, not a scorer

On nights without football, I read numbers one by one. And Nembhard's profile reads very clearly.

He averaged 6.6 points, 2.2 rebounds and 5.3 assists in 19.5 minutes per game. The assist figure is the part worth discussing. Projected to 36 minutes, that rate equals roughly 9.8 assists — a level very few backup guards in the league reach.

Six games with at least 10 assists. Four double-doubles. And one 23-assist game against Chicago.

Nembhard's statistical profile is that of a pure playmaking guard, not a scoring guard. He creates chances for others rather than generating his own points. That distinction is not minor, because it determines where he plays, with whom, and for how many minutes.

But the missing data outweighs the data that exists.

No TS%. No eFG%. No USG%. No plus-minus. No turnover data. No defensive metrics. That means we know how many assists he produced, but not whether those assists were high-value creation or simply the product of the volume of ball he handled.

That is a serious blind spot for a player expected to share the floor with stars. If Nembhard carries no gravity from beyond the arc, his playmaking will be confined to lineups where he is the sole ball-handler. With Murray on the floor, that almost never happens.

Measured against the norm for a league-average backup guard, Nembhard sits above average in per-minute assist creation and below average in scoring volume. That is not a bad profile. It is a narrow one.

Viewers see a play. I see an opening gambit. When Denver slots Nembhard third or fourth in the guard rotation, they are not buying a complete player. They are buying a specific function: ball-handling while Murray rests.

Within Denver's offensive system, the ball typically runs through Nikola Jokić at the top of the key. When Murray sits, the team loses its second pick-and-roll pressure creator. Nembhard does not generate scoring pressure, but he can hold the rhythm. During those minutes, Denver does not need him to score 15. They need him not to disappear from the game.

On the age curve, Nembhard is ascending. Twenty-three is precisely the typical development window for a lead guard. Short-term decline risk is low. But one paradox is worth remembering: small guards who live on quickness and space decline far faster than guards with size and a jump shot once athleticism begins to slip. That is a long-term risk, not a next-season risk.

Contrarian angle: the 23-assist game is a trap

There is one way of reading Nembhard's profile that I want to put on the scale and then flip over.

The 23-assist game against Chicago is an extreme outlier, and using it as evidence of his long-term ceiling is a methodological error. One game does not make a profile. If Denver's front office made its decision based on that night, it bought a memory, not a skill.

The correct reading lies elsewhere. Nembhard's value is not in the peak of a single game but in his per-minute consistency across 60 games. That consistency — not the number 23 — is what convinced a contending team to trade away a development slot.

And here a larger problem emerges, one belonging to the league's structure.

Small guards who cannot shoot get schemed off the floor. In the postseason, opponents will ignore him off the ball, load up on Jokić, and force Denver to choose between spacing and organization. In playoff basketball, that is not a choice. It is a sentence.

So why did Denver do it? Because they are constrained by the salary sheet. A team near the apron cannot buy depth with cash. It has to buy it with two-way slots, with the draft, with small bets.

One detail I consider important carries only low confidence: both his career-high scoring game and one of his best assist games came against Denver. The Nuggets scouting department may already hold an internal file on him thicker than those on other two-way names. That is a reasonable hypothesis, not a conclusion.

It is also worth stating the league landscape plainly. This transaction does not change the Western Conference hierarchy. Denver's real variables — Jokić's health, Murray's availability, bench production — matter far more than one two-way slot. If Nembhard succeeds, he improves backcourt depth in the event injuries hit. If he fails, Denver loses essentially nothing.

What to watch: the try-before-you-buy mechanism

A two-way contract operates as a try-before-you-buy mechanism. If Nembhard exceeds the NBA service-day limit attached to a two-way deal, Denver will be forced to convert him to a standard contract. That mechanism is smooth, and it gives the team a live inspection before any long-term commitment.

What I want to see is not another 20-assist game. I want to see shooting data. If Nembhard proves he can stand in the corner and force defenders to respect him, his value changes entirely. If not, he will remain a regular-season contingency and a name struck from the rotation by April.

What people call instinct, I call an encoded trace. Denver has just encoded a new trace into its bench. The question is not whether it works in November. The question is whether it still exists in May.